Your transfer history says successful, but you can't see the balance in your wallet. Where did the crypto you just sent go? Don't worry — the tokens have actually arrived on-chain. Binance Web3 Wallet usually doesn't show them for only two core reasons: you haven't manually added the token's contract address, or your wallet's current network doesn't match the blockchain used for the transfer. This article teaches you how to find hidden tokens in two minutes.

The world's largest cryptocurrency exchange by trading volume,leading in security and liquidity.
New user benefit: Enjoy 20% off trading fees upon registration!
Step 1: Confirm which chain you transferred on
Open the Binance app, go to "Assets" - "Spot" or "Funding", find your withdrawal record (or the transaction hash from an external wallet), and confirm two key things:
Chain name: Confirm whether it is BSC, Ethereum, Polygon, Solana, or another public chain
Token contract address: For EVM chain tokens such as ERC20 or BSC, the transaction record usually shows the corresponding contract address. You can also look it up on a block explorer.
Note: As long as the transfer shows success, you don't need to worry. It has nothing to do with chain congestion or gas fees. The tokens are already on-chain. The wallet not showing them is only a display issue, not lost funds.
Step 2: Switch your wallet network to the correct chain
Make your wallet enter the environment of the chain you used for the transfer. Here's how:
App: Open the Binance Web3 Wallet home page, tap the network name shown at the top center or top right, find the public chain that matches your transfer in the drop-down list, and select it.
Plugin/Extension: Click the browser extension icon, find the network drop-down menu at the top, and switch directly to the matching public chain.
After that, check that the network name at the top of the home page exactly matches the chain name in your transfer record.
If your target chain is not in the default list (for example, some new public chains or Layer 2 networks): The Binance Web3 Wallet extension supports manually adding a custom network, but the App does not yet support this. If you can't find the corresponding network in the App, use the browser extension, or export your wallet to another wallet that supports that chain.
Custom network path: Click the network drop-down menu in the extension - Switch network - Custom tab - Add custom network. Enter the RPC URL, chain ID, and token symbol provided by the official public chain documentation. Note that custom networks will not automatically sync to the mobile App.
Step 3: Manually import the token contract address
After switching to the correct network, it is normal if the token still doesn't show. Most non-mainstream tokens require users to manually tell the wallet which asset the contract belongs to.
Steps:
On the Binance Web3 Wallet home page, scroll down to the asset list area and tap the "Manage Tokens" button.
Tap the "+" icon in the top right corner of the page.
Key check: The network selection must be the matching public chain you just switched to. For example, if the transfer used BSC, you must select BSC here.
In the "Contract Address" input box, paste the correct contract address copied from your transfer record or the project's official website.
Tap "Import". The Binance wallet will automatically recognize the token symbol and decimals.
After import, the page will show "Import successful", and you can see the token name and balance in the token list.
Common failure reasons
Failure 1: Wrong network selected. This is the most common issue. The public chain used for the transfer must match the network selected when importing the token exactly. For example, if you transferred USDT on Ethereum mainnet ERC20, but switch to BSC in the wallet to import the token, you will never see the balance.
Failure 2: Contract address copied incorrectly. Do not fill in an address from memory. Go to a block explorer for the relevant chain, such as BscScan or Etherscan, search for the token, and use the contract address shown on the official page. Make sure there are no extra spaces before or after the address.
Failure 3: The App does not support that network. The Binance Web3 Wallet App can automatically recognize most mainstream tokens, but support for some new chains or non-EVM assets such as BRC-20 is slower. You can use the earlier method of exporting your private key to another compatible wallet.
Risk reminder: Contract addresses found through online search may be fake. Always get contract addresses from the project's official channels or trusted platforms such as CoinMarketCap. Importing a fake contract address will not directly cause your funds to be stolen, but it may display fake token information and mislead later transactions. When adding a custom network, a malicious RPC node may forge on-chain data. Always get official RPC information from the public chain's official documentation.

The world's largest cryptocurrency exchange by trading volume,leading in security and liquidity.
New user benefit: Enjoy 20% off trading fees upon registration!
Final check
After completing the three steps above, return to the wallet home page, pull down to refresh, and the token balance should display normally. If it still doesn't show, re-check the network and contract address information in Step 2 and Step 3.


