MetaMask Shows 0 Balance After Adding a Token? How to Check On-Chain

 / 
2

If MetaMask shows a balance of 0 after adding a token, don't add it again. First, open a blockchain explorer and check the actual on-chain data. If the explorer shows a balance, then troubleshoot the network and RPC settings in your wallet. If even the explorer shows no balance, the transfer itself may not have succeeded—fixing the wallet further won't help.

Prerequisites

  • The token contract address you want to check (not the transaction hash from a record, but the contract address of the token itself).

  • The corresponding blockchain explorer URL: Etherscan for Ethereum, Bscscan for BSC, Polygonscan for Polygon.

Step 1: Check the Balance on a Blockchain Explorer

This is the foundation for all subsequent steps; skipping it is like troubleshooting a network blindfolded.

Copy your MetaMask wallet address. Open the blockchain explorer for the relevant network, paste the address, and search.

How to Interpret the Results

  • If the token is the network's native token (e.g., ETH, BNB, MATIC), the balance will be displayed directly on the account overview page.

  • If it's another token (e.g., USDT, UNI), look at the "Tokens" dropdown menu and find the corresponding name. Click the token and verify that the contract address matches the one you added in MetaMask.

Verification step: The specific number shown for the token on the explorer page is your wallet's actual on-chain balance.

Step 2: Verify You're on the Correct Network

If the explorer shows a balance but the wallet shows 0, the most common reason is that the wallet is connected to a different network than the token's network. For example, you sent USDT on BSC to your wallet, but MetaMask is currently connected to Ethereum Mainnet. That address has no USDT on Ethereum, so it naturally shows 0.

What to Do

Tap the current network at the top of MetaMask and switch to the network where the token actually resides. If you're unsure which network, check the transfer record or the network identifier in the explorer.

Verification step: The network name displayed at the top of the wallet matches the network where the balance appears in the explorer.

Step 3: Manually Add or Re-import the Token

If it still doesn't show after switching networks, you need to manually import the token. MetaMask's official help center clearly states that the wallet does not automatically detect all tokens, especially newly launched or less common ones—they must be added manually.

How to Do It

  1. At the bottom of the "Assets" tab in MetaMask, click "Import tokens".

  2. Switch to the "Custom token" tab.

  3. Paste the contract address you copied from the explorer in Step 1. MetaMask will automatically fill in the token symbol and decimals.

If it still shows 0 after importing, try removing the token (long press or right-click in the asset list to hide it), then re-import.

Verification step: The token name appears in the asset list with a balance figure that matches the explorer.

Step 4: Switch RPC Node (When the Wallet Data Is Out of Sync)

If the explorer shows a balance and you've followed the steps above but the wallet still shows 0—the RPC node might be stuck and not syncing the latest data.

How to Do It

In MetaMask's "Settings" → "Networks", find the current network and change to an alternative RPC URL. Backup RPC addresses vary greatly between blockchains; check the official documentation or community of that network.

Verification step: After switching the RPC, force refresh the wallet (switch to another network and back), and the balance should appear.

Common Reasons for Failure

MetaMask has a known behavior: it allows you to import a token's contract address on network A even if the token is deployed on network B—no error is shown, and the balance remains 0. This means you may have accidentally added a token from the wrong network. If you've imported the same address three times with no balance, stop and check: which chain is this token contract actually deployed on?

Risk Warning

When checking balances on a block explorer, always verify that the token contract address comes from the project's official website. Scammers frequently create tokens with the same name and deploy fake contracts, then use airdrops to phish. If you copy a fake contract address and import the fake token, interacting with it (transfers or approvals) may lead to asset theft. A balance in the block explorer does not prove the token is genuine—confirm the contract address is correct first.

Verification After Completion

Open the block explorer again, search your wallet address, and take a screenshot of the balance page. Then open MetaMask and compare the numbers. If they match, the issue is resolved. If not, wait 30 seconds, refresh both the explorer and the wallet, and compare once more.