A balance is a view of chain state
Assets & Transactions is designed around clear network awareness. A wallet interface presents blockchain state and signing requests, while the assets themselves remain recorded on their respective networks.
Reading transaction history
Before receiving or sending, verify the network and address. Before broadcasting a transaction, also review the amount and estimated fee; after broadcast, keep the transaction hash for independent verification.
Verify token contracts
Token visibility depends on network and contract information. Matching names or symbols are not enough to identify a token, so contract addresses should come from trusted sources.
Public ledgers and privacy
Seed phrases and private keys remain with the user. imtoken does not ask users to enter them into ordinary web pages, and on-chain transactions generally cannot be unilaterally reversed by the wallet.
How to verify Assets & Transactions information
Separate what an interface displays from what the blockchain records. Note the network, public address, and transaction hash, then inspect the correct explorer for block inclusion, fees, status, and contract events. Token and cross-chain questions may require checking contract addresses and both source and destination networks.
Common misconceptions
Common mistakes include treating same-named tokens as identical, checking an address without checking the network, assuming a wallet connection equals approval, treating gasless signatures as harmless, or relying on a page banner instead of on-chain status.
Practical verification for Assets & Transactions
A practical way to work with Assets & Transactions is to separate preparation, review, execution, verification, and maintenance. Start by identifying the active network and account, then use A balance is a view of chain state, Reading transaction history, and Verify token contracts as checkpoints for the address, asset, contract, fee, or permission involved. After an action is broadcast, keep the transaction hash and verify it on the correct network. When a DApp or smart contract is involved, also review persistent approvals after the session ends. Public addresses and transaction hashes are appropriate troubleshooting references; seed phrases, private keys, and verification codes are not. Any workflow that asks for those secrets should be stopped and independently rechecked.
On-chain transactions generally cannot be reversed by a wallet provider. Review the address, network, amount, contract, and requested permissions before signing.