basiliskawakens.xyz

Why Does a Wallet Show a Token Balance but the Explorer Says Zero?

The short answer is that the wallet and the explorer are almost certainly looking at different pieces of data. A wallet interface usually reads the balance from the token contract itself, while a block explorer's token tab often reads from a database of parsed transfer events. When those two views disagree, the error is usually in the explorer's indexing, not in the token contract. But there are a few other common reasons, and you need to rule them out before assuming the explorer is wrong.

The explorer's indexer is the usual suspect

Block explorers like Etherscan do not compute token balances on the fly. They run an indexer that scans every block, decodes every ERC-20 Transfer event, and updates a database. That database powers the "Token" tab on an address page.

If the indexer misses a transfer - because it was in a deeply buried transaction, part of a chain reorganization, or just too recent - the database shows zero even though the contract state says otherwise.

Your wallet, by contrast, typically calls the token contract's balanceOf(address) function directly. That reads the actual storage slot on the blockchain. No indexer involved. That's why the two can disagree.

What to do: Check the token contract address, not the symbol. Then look at the "Holders" tab on the explorer for that specific contract. If the explorer's holder list shows the balance, but the address page token tab shows zero, it's an indexing lag. Wait a few minutes or clear the explorer's cache.

You Might Be Looking at the Wrong Network

This is the most common user error. A wallet like MetaMask can be pointed at Ethereum mainnet, but you might be viewing an address that holds tokens on Polygon, Arbitrum, or BNB Chain. The wallet often auto-detects the network and shows the correct balance. The explorer, however, might be showing you the mainnet view by default.

For example, an address holding USDC on Polygon will show a zero USDC balance on Etherscan's mainnet page. The same address on Polygonscan shows the correct amount.

What to do: Verify the network at the top of the explorer page. Look for the chain name and the block number. Match it to the network your wallet is currently connected to.

The Token Is Held in a Different Contract

Your wallet might show a balance because it is reading from a proxy contract, a staking vault, or a wrapped token contract. The explorer's token tab might be looking at the underlying asset.

A classic case: you hold aWETH (Aave Wrapped ETH) in your wallet. Your wallet displays it as a token. The explorer's token tab also shows aWETH, but if you filter for WETH itself, it shows zero. The token is not "lost" - it's just that the balance lives in a different contract's accounting.

What to do: Look at the token contract address in your wallet. Then go to the explorer, search for that contract, and check the "Holders" or "Token Tracker" page. If your address is listed there, you own the token. The explorer's address page might simply not be aggregating that particular contract.

The Token Is a Rebasing or Fee-on-Transfer Token

Some tokens change their total supply or redistribute balances on every transfer. These are often called rebasing tokens (like AMPL) or fee-on-transfer tokens (like SAFE or any token with a transfer tax).

Your wallet might be fetching a stale balance from a cache. The explorer, on the other hand, reads the live balanceOf from the contract. With rebasing tokens, the balance changes every few hours. If the explorer's indexer hasn't caught up to the latest rebase, it shows an old balance - or zero if the rebase is aggressive.

What to do: Read the balanceOf directly on the token contract's "Read Contract" page on the explorer. That is the ground truth. If that shows a number, you own the tokens. The explorer's token tab is just lagging.

The Token Was Sent to the Wrong Address (or Burned)

If you accidentally sent tokens to the contract itself, a burn address, or a non-existent address, the explorer might show zero because the tokens are unrecoverable. Your wallet might still show a "ghost" balance if it has cached the previous transaction.

This is not a balance discrepancy - it's a permanent loss. The explorer is correct; the wallet is showing stale data.

What to do: Refresh the wallet. If the balance persists, check the token contract's "Holders" list. If your address is not there, the tokens are gone.

The Explorer Is Showing the "Internal" Balance, Not the ERC-20 Balance

Some explorers have a "Token" tab and a separate "Transactions" tab. The token tab might show only native coin (ETH, BNB) transfers, not ERC-20 activity. If you filtered or toggled a setting, you might be looking at the wrong view.

What to do: Look for a dropdown or filter labeled "Token Transfers" or "ERC-20." Make sure you are not on the "Transactions" (native coin) tab.

How to Check the Ground Truth Yourself

If you are still stuck, do this:

  1. Go to the token's contract address on the explorer.
  2. Click "Contract" then "Read Contract."
  3. Scroll to balanceOf.
  4. Paste the wallet address.
  5. Click "Query."

The result is the exact balance the token contract holds for that address. If it returns a number, the tokens exist. If it returns zero, the tokens are not there - regardless of what your wallet says.

If the query returns a number but the explorer's token tab shows zero, the indexer is broken. You can also cross-check with a second explorer (e.g., Etherscan vs. Blockscout) for the same network.

Why wallets sometimes show the wrong number

Wallets cache balances. They also often call balanceOf in the background, but they may not refresh on every block. If you received tokens within the last minute, the wallet might show zero until it manually refreshes. The explorer, by contrast, updates its database every block, so it might show the balance before the wallet does.

The reverse is also true: the wallet might be showing a cached balance from before a transfer, while the explorer has already processed the outgoing transaction.

The Bottom Line

A wallet showing a balance while an explorer shows zero is almost always an indexing or caching issue. The token contract is the source of truth. Use the balanceOf read function to verify. If the contract says zero, the tokens are not in that wallet. If the contract says otherwise, the explorer is behind, and you can safely ignore its token tab.

Not financial advice. basiliskawakens.xyz publishes market data and general information about digital assets. Crypto assets are volatile and you can lose everything you put in. Nothing here is a recommendation to buy, sell or hold, and we make no price predictions.

Prices are sourced from third parties and may be delayed or wrong. Verify anything you intend to act on against a primary source.

Back to on-chain data