On this page
why asset displays can differ
Wallet balances depend on reading blockchain data, so indexing delays, network changes or unrecognized tokens can create temporary display differences. This matters in practice because blockchain outcomes are determined by the selected network and the request that is signed, not merely by what a button is called. For why asset displays can differ, prioritize information you can verify: the active network, public address, contract target and transaction status. Turning those details into a repeatable checklist is more reliable than reacting to vague interface messages.
Token names and icons are not unique identifiers. The contract address provides much stronger evidence of which asset is being viewed. It also helps to separate three layers: what the wallet displays, what the network has actually recorded, and what a third-party service claims. When something looks wrong, identify the layer first and then verify with a transaction hash, block explorer or explicit network parameters. No legitimate why asset displays can differ workflow requires a seed phrase, private key or verification code to be sent to another person.
token contracts and asset identification
Token names and icons are not unique identifiers. The contract address provides much stronger evidence of which asset is being viewed. It also helps to separate three layers: what the wallet displays, what the network has actually recorded, and what a third-party service claims. When something looks wrong, identify the layer first and then verify with a transaction hash, block explorer or explicit network parameters. No legitimate token contracts and asset identification workflow requires a seed phrase, private key or verification code to be sent to another person.
For reconciliation, compare the transaction hash, block, sender, recipient, token contract and event logs rather than relying on one portfolio screen. If the action includes a signature, approval or contract call, inspect the permission scope and possible asset impact separately. Friendly labels are not a substitute for the underlying request. Check the target, asset, amount or allowance, network and final confirmation details before proceeding. This sequence reduces mistakes caused by urgency, phishing or the wrong network.
- Verify the network, address and public on-chain information relevant to token contracts and asset identification.
- Never send a seed phrase, private key or verification code to anyone.
- For DApps or contracts, review each signature and approval scope separately.
transaction history and block explorers
For reconciliation, compare the transaction hash, block, sender, recipient, token contract and event logs rather than relying on one portfolio screen. If the action includes a signature, approval or contract call, inspect the permission scope and possible asset impact separately. Friendly labels are not a substitute for the underlying request. Check the target, asset, amount or allowance, network and final confirmation details before proceeding. This sequence reduces mistakes caused by urgency, phishing or the wrong network.
Wallet balances depend on reading blockchain data, so indexing delays, network changes or unrecognized tokens can create temporary display differences. This matters in practice because blockchain outcomes are determined by the selected network and the request that is signed, not merely by what a button is called. For transaction history and block explorers, prioritize information you can verify: the active network, public address, contract target and transaction status. Turning those details into a repeatable checklist is more reliable than reacting to vague interface messages.
reconciliation and display troubleshooting
Wallet balances depend on reading blockchain data, so indexing delays, network changes or unrecognized tokens can create temporary display differences. This matters in practice because blockchain outcomes are determined by the selected network and the request that is signed, not merely by what a button is called. For reconciliation and display troubleshooting, prioritize information you can verify: the active network, public address, contract target and transaction status. Turning those details into a repeatable checklist is more reliable than reacting to vague interface messages.
Token names and icons are not unique identifiers. The contract address provides much stronger evidence of which asset is being viewed. It also helps to separate three layers: what the wallet displays, what the network has actually recorded, and what a third-party service claims. When something looks wrong, identify the layer first and then verify with a transaction hash, block explorer or explicit network parameters. No legitimate reconciliation and display troubleshooting workflow requires a seed phrase, private key or verification code to be sent to another person.
- Verify the network, address and public on-chain information relevant to reconciliation and display troubleshooting.
- Never send a seed phrase, private key or verification code to anyone.
- For DApps or contracts, review each signature and approval scope separately.