The Transfer Arrived—Why Does the Wallet Still Show Zero?

A wallet application is an interface to blockchain accounts, not the final source of truth. A zero display can mean that no transaction exists, the transfer is still confirming, the user opened a different address, the wallet is on another network or the token was not detected. Locate the asset before trying to resend or import anything.

Use the Balance Location Ladder

Move from public evidence to local display.

• Transaction exists and is confirmed
• Destination address matches an account you control
• Blockchain network is correct
• Native coin or token contract is identified
• The correct wallet account is open
• The token is visible in the interface
• The wallet is synchronized with a working network endpoint

Start with the transaction hash

If the sender supplied a hash, open the explorer for the claimed network and inspect status, destination, asset and amount. No hash can mean that a custodial sender has not broadcast the withdrawal or that the payment was internal rather than on-chain.

Pending is different from missing

MetaMask recommends checking whether the transaction has confirmed before diagnosing the display. A pending transfer can appear in an explorer while remaining unavailable in the final wallet balance.

Compare the complete receiving address

Confirm that the explorer destination is the exact address currently open in the wallet. A user can accidentally view another account, a watch-only address or an account restored from a different recovery phrase.

Open the network where the asset arrived

A token exists only on the blockchain that recorded the transfer. MetaMask states that the balance must be viewed on the correct network. Switching the interface does not move the asset; it changes which ledger the wallet is reading.

Identify native coin versus token contract

ETH, BNB, TRX and similar native assets appear through the network balance. ERC20-style tokens require a contract address and metadata. A ticker alone is insufficient because unrelated contracts can use the same symbol.

Token detection can fail even when ownership is correct

MetaMask explains that an explorer can confirm a token balance while the wallet fails to display it automatically. Import the token only after verifying the contract through an authoritative project or explorer source.

Restored wallets may omit additional accounts

MetaMask documents that accounts derived from the same recovery phrase may need to be recreated in sequence, while imported accounts require their original private key or file. The asset can belong to a legitimate old address that the current interface has not added.

An incorrect fiat value is not a missing asset

Price feeds can fail or ignore an obscure token while the on-chain amount remains visible. Separate token quantity from dollar valuation before concluding that the balance vanished.

RPC or synchronization problems affect the interface

If the explorer shows the correct asset but several wallet views remain stale, restart the application, update it from the official source and test a trusted network endpoint. Never reveal recovery access to someone offering remote repair.

Wrong-network receipt can still be recoverable

When an EVM-compatible address is controlled by the same key, the asset may be accessible by adding or switching to the actual network. A custodial destination or incompatible chain requires a different recovery analysis.

Do not resend as the first fix

A second transfer creates another fee and another opportunity for the same address or network error. Resolve the location of the first asset before moving more value.

Worked location trace

The explorer confirms a USDT transfer to the correct EVM address on BSC. The wallet is displaying Ethereum and has not detected the BSC token contract. Switching to BSC and adding the verified contract restores the visible balance without another transaction.

Escalate only after collecting evidence

Provide the sender or wallet support with the transaction hash, destination, network, token contract, confirmation status and the account address displayed in the application. Never include a recovery phrase or private key.

Current conclusion

A missing display does not prove a missing asset. Use the explorer to locate the transaction, then align the wallet’s account, network and token contract with the public blockchain evidence.

Evidence boundaries

The current MetaMask help centre supports the transaction, chain, token-detection and restored-account sequence used here. Other wallet interfaces may label these controls differently.

Missing-asset diagnostic references — July 29, 2026

Transaction display, network and account-restoration documentation was prioritized.

• MetaMask incorrect or missing token balance: https://support.metamask.io/manage-crypto/tokens/what-to-do-when-your-balance-of-tokens-is-incorrect
• MetaMask wrong-network transfer guidance: https://support.metamask.io/manage-crypto/move-crypto/send/funds-sent-on-wrong-network/
• MetaMask restored missing accounts: https://support.metamask.io/configure/accounts/how-to-add-missing-accounts-after-restoring-with-secret-recovery-phrase
• MetaMask backup and synchronization: https://support.metamask.io/configure/wallet/account-backup-and-sync/

FAQ