Start your 3-day free trial
Sign up to experience all premium features at no cost.
*Available only to new users. Each user is limited to one trial.


If a token does not appear in your crypto wallet, do not import the first contract address you find or restore the wallet somewhere else. First verify whether the transfer exists on the intended blockchain, belongs to your address, and uses the token contract you expected; only then troubleshoot the wallet's display.
Key Takeaways
- A wallet screen is a view of blockchain data, not the final record of ownership.
- Check the transaction, receiving address, network, and token contract independently.
- Adding a custom token changes the wallet display; it does not move or recover funds.
- Never enter a seed phrase or private key into a token-import page or support form.
The online security guide explains the independent-channel habit used throughout this checklist: open the wallet, explorer, and issuer source yourself instead of following a link from an unsolicited message.
“Missing” can describe several different states. The transfer may still be pending, it may have failed, it may have gone to another account, or it may exist on a network your wallet is not currently showing. The token can also be present on-chain while the wallet has not indexed it or has hidden it as an unknown asset.
MetaMask recommends checking confirmation, the selected network, and the balance on a suitable block explorer before treating a token as absent. It also notes that a token can be on the address without being detected automatically by the wallet.[1]
| Evidence | What it can establish | What it cannot establish |
|---|---|---|
| Sending-app receipt | A transfer was requested | That it was broadcast or confirmed |
| Transaction hash | A public transaction can be queried | That you selected the right network |
| Network explorer | Status, addresses, contract, and amount on that chain | Another chain's state or a custodian's ledger |
| Wallet asset list | What the app currently displays | Complete ownership across every network |
| Official issuer directory | Expected token identity for a named network | Your personal receiving address |
Do not jump directly to “wallet bug.” Identify which row contains the first mismatch.
Open the sending wallet or exchange through its known app or bookmarked site. Copy the full transaction hash, not an order number, withdrawal reference, screenshot, or shortened address.
If no public transaction hash exists, the transfer may still be inside the sender's system. Follow the platform record rather than searching random explorers. The confirmed-deposit guide covers the opposite case, where the chain has recorded a deposit but a custodian has not credited its internal balance.
Determine the network from the original transfer record. Ethereum, Tron, Solana, Arbitrum, and other networks have separate state even when a token uses the same name.
Open a reputable explorer independently and search the full hash. Confirm that the transaction succeeded, reached your full receiving address, transferred the expected amount, and identifies the expected token contract. A “success” label on the wrong chain does not put the asset on the chain currently selected in your wallet.
Wallet apps can contain multiple accounts derived from one recovery phrase, imported accounts controlled by separate keys, hardware-wallet accounts, and watch-only addresses. Compare the complete receiving address from the explorer with the complete address currently open in the wallet.
Do not compare only the first and last four characters when resolving a discrepancy. Address poisoning and ordinary copy mistakes can produce strings that look familiar at the edges. Copy both values into a plain comparison tool you trust, without exposing private material.
A token exists within a particular network's state. Switch the wallet to the chain shown by the confirmed transaction and make sure the wallet supports that network.
If the transfer used an unintended network, stop. Adding a similarly named network or token will not bridge the asset. Use the separate wrong-network USDT checklist to determine custody and any official recovery route.
Anyone can create a token with a familiar name, ticker, and icon. Obtain the contract or asset identifier from the issuer's independently reached official documentation, then compare the complete value with the explorer record.
Tether, for example, lists different USD₮ identifiers for supported protocols.[2] That is why a ticker such as “USDT” is not enough. The expected network and its exact identifier must be treated as one identity.
Restart or refresh the wallet using its normal controls. Check whether the asset is hidden, filtered as spam, or excluded from the selected portfolio view. If the wallet supports manual token display, paste the already verified contract through the wallet's built-in import flow.
MetaMask describes custom-token addition as a display action and warns users to verify the token before adding it.[3] Adding the entry does not create a balance, retrieve a failed transfer, or authorize anyone to move funds.
Wallets depend on RPC providers, token lists, indexers, cached portfolio data, and spam filters. Any of those layers can lag, omit a small asset, or disagree about metadata while the underlying chain state remains unchanged.
The explorer can also be wrong for your question if you opened the wrong network, a copied phishing site, or a page for a look-alike contract. Verify the explorer hostname and chain rather than accepting a polished result page.
Some wallets display only widely recognized assets automatically. Others hide unsolicited tokens because attackers use token names and embedded URLs to lure recipients into malicious sites. The crypto dusting guide explains why an unknown asset should often be hidden rather than used.
Never type a recovery phrase, seed phrase, private key, password, or one-time code into an explorer, token page, direct message, or remote-support session. Public-chain lookup needs only public identifiers.
Do not send another transfer merely to “activate” the first one. Do not approve token spending, sign an unexplained message, or connect to a site printed in an unsolicited token's name. Display and authorization are separate actions.
Avoid deleting wallet data or reinstalling until you have confirmed that your recovery material is valid, private, and backed up according to the wallet vendor's official procedure. A display problem is not a reason to expose the keys that control every asset in the account.
Contact the wallet vendor when the correct address, network, contract, and on-chain balance all match but the app still cannot display the asset. Provide the public address, transaction hash, network, wallet version, and a redacted description of the display behavior.
Contact the sender or exchange when no transaction hash exists, the transaction failed, the destination differs, or the withdrawal record remains internal. Use the official in-app channel and keep one evidence package instead of opening conflicting tickets.
Yes. If the correct network explorer shows the verified token contract and a balance for your exact address, the app may simply be missing or hiding that display entry. Confirm every identifier before importing it.
No. It tells the wallet how to display an existing token contract. It cannot reverse a failed transfer, move an asset between networks, or change the balance recorded on-chain.
Each blockchain keeps separate state. A token received on one network does not automatically appear on another, even when both networks use compatible address formats.
No. Reach the issuer or project's official documentation independently and verify the network-specific identifier. Search ads, copied lists, token logos, and social posts can point to look-alike contracts.
Yes. Network connectivity and automatic token discovery are different functions. A wallet may connect to a chain while requiring a verified custom-token entry or hiding an unrecognized asset.
Not by itself. Public addresses can receive tokens without permission. Do not interact with an unknown token, and check the chain history for unauthorized outgoing activity separately.
Treat it as a destination problem, not a display problem. Determine who controls that address and contact the sending service through its official channel; importing a token cannot redirect the transfer.
Not at the blockchain layer. A VPN cannot change blockchain state, token contracts, wallet keys, or a custodian's ledger. However, enabling, disabling, or changing a VPN can alter access to an RPC or indexing service and may let the wallet interface refresh. Treat that as a display-path change, then verify the transaction and balance independently on the intended network.
Disclaimer: This article provides general technical and consumer information, not financial, legal, or recovery advice. Blockchain transfers may be irreversible, and recovery options depend on the network, wallet, and custodian.
Sources:
Sources checked 9 September 2026.
Related articles:
Sign up to experience all premium features at no cost.
*Available only to new users. Each user is limited to one trial.





