The asset list is a view of blockchain state
A wallet assembles an asset view from the account address, active network, token contracts, and indexing data. The assets themselves remain on-chain, so a display problem does not automatically mean the asset has disappeared.
Start by confirming the address and network, then verify the relevant token contract and transaction history.
A token name or ticker is not a unique identifier
Different contracts can use the same or very similar names and symbols. The network and contract address are the more reliable identifiers, and parameters such as decimals affect how quantities are displayed.
Do not transfer or approve an unfamiliar token simply because its icon or ticker resembles a well-known asset.
Transaction history includes more than simple transfers
A transaction may represent a native transfer, token transfer, NFT action, approval, swap, or another contract call. A simplified wallet label may not show every event or internal operation.
Use the transaction hash when you need to inspect the destination, method, event logs, execution result, and fee on the correct network.
Display latency and chain confirmation are different
A transaction can be confirmed on-chain while the wallet’s balance or activity feed updates later because of node, cache, or indexing delays. The reverse is also true: “submitted” in the interface is not the same as confirmed.
Treat chain confirmation and interface refresh as separate questions when troubleshooting.
Unexpected tokens can be spam or a lure
Addresses sometimes receive unsolicited tokens or NFTs that include names, notes, or links designed to push the user toward an external site. Do not enter recovery material or sign unexplained approvals just to “claim,” “unlock,” or “sell” an unknown asset.
Seeing an unsolicited asset usually does not require immediate contract interaction.
Reconciliation uses public evidence, not wallet secrets
Public addresses, transaction hashes, block numbers, and network names are appropriate for record checking. Seed phrases, private keys, and verification codes are not reconciliation data and should not be provided to a third party.
Most cross-device or cross-tool verification can be completed with public chain information alone.
Public addresses and transaction hashes can be shared for chain verification. Seed phrases, private keys, and verification codes should never be used as proof of asset ownership to a support page.
A structured check for a missing or incorrect balance
Confirm the account first, then the network, token contract, and transaction hash. If the chain shows a confirmed balance change but the wallet has not refreshed, allow for indexing delay before attempting recovery or re-importing the wallet.
Separate a display issue from an on-chain issue
For same-name tokens, unsolicited airdrops, or unfamiliar NFTs, trust the network and contract data rather than an icon, name, or external link.
- Confirm the account and network before judging the displayed balance.
- Use the contract address to distinguish same-name tokens.
- Use transaction hashes to verify execution, fees, and events.
- Do not interact with unsolicited assets just because they contain a link or claim.