imtoken will never ask for your seed phrase, private key or verification code. Always review the address, network and request details before transferring, signing or approving.
imtoken
中文Download
Practical Guide

Assets & Transactions

This guide connects the practical decisions behind asset display, token contracts, and transaction history. It focuses on verifiable on-chain information, clear user actions, and security habits that remain useful even when interfaces change.

Download imtokenSecurity guide →
Before you begin

Use a fixed sequence for the goal, network, address and expected result instead of relying on defaults.

Before you begin

Prepare a check sequence before acting

Confirm the goal, account, network and expected result before you send, sign, connect or approve.

On this page
  1. Prepare before you start
  2. Understand asset display and token contracts
  3. Work through transaction history and transaction status carefully
  4. Verify the on-chain result
  5. Troubleshooting common mistakes
  6. Good habits after the task is complete

Prepare before you start

Before using this assets & transactions guide, identify the account, network, asset, and exact outcome you want. Similar-looking addresses do not make two networks interchangeable, and a wallet interface cannot automatically correct a transfer that was sent on the wrong chain; in Assets & Transactions, read this specifically alongside “Prepare before you start” and asset display. A clear task definition makes every later check more meaningful; in Assets & Transactions, read this specifically alongside “Prepare before you start” and asset display. This part of Assets & Transactions should be read together with the surrounding workflow: asset display affects how you interpret token contracts, while transaction history helps confirm the state after the action.

Understand asset display and token contracts

Start by understanding how asset display and token contracts affect the operation. Do not rely on a default network or an autofilled address for a high-value action; in Assets & Transactions, read this specifically alongside “Understand asset display and token contracts” and token contracts. Confirm the network, destination, token contract when relevant, and the account that will sign; in Assets & Transactions, read this specifically alongside “Understand asset display and token contracts” and token contracts. For a first-time workflow, a smaller test can help you understand the sequence, but the same checks are still required; in Assets & Transactions, read this specifically alongside “Understand asset display and token contracts” and token contracts. For Assets & Transactions, connect token contracts with transaction history and transaction status; the important part is the relationship between those concepts and the on-chain evidence you can verify afterward.

Pre-action checklist
  • Confirm the intended account and network.
  • Verify the address, contract or DApp independently.
  • Know what will change after the request is confirmed.

Work through transaction history and transaction status carefully

When you reach transaction history and transaction status, read what the wallet is actually asking you to approve. A DApp connection is not blanket consent for later signatures; in Assets & Transactions, read this specifically alongside “Work through transaction history and transaction status carefully” and transaction history. If a contract, permission, amount, or destination differs from what you expected, cancel the step and restart from a trusted entry point instead of trying to “fix” an unclear request in place; in Assets & Transactions, read this specifically alongside “Work through transaction history and transaction status carefully” and transaction history. When working through “Work through transaction history and transaction status carefully,” check the source, network, request details and resulting state in that order, with extra attention to transaction history and transaction status.

Verify the on-chain result

After submission, verify the result with the transaction hash rather than trusting only a success toast; in Assets & Transactions, read this specifically alongside “Verify the on-chain result” and transaction status. The explorer should show the network, sender, recipient, fee, status, and confirmation progress; in Assets & Transactions, read this specifically alongside “Verify the on-chain result” and transaction status. For steps involving blockchain explorers, the process may include waiting periods or multiple stages, so the first wallet notification is not always the final on-chain state; in Assets & Transactions, read this specifically alongside “Verify the on-chain result” and transaction status. Do not treat an interface success message as the final answer for Assets & Transactions. Use transaction status, blockchain explorers and troubleshooting to confirm that the expected change occurred on the intended network.

Troubleshooting common mistakes

Common mistakes include the wrong network, a copied address error, an incorrect token contract, insufficient gas, duplicate submissions, and confusing a connection request with a transaction; in Assets & Transactions, read this specifically alongside “Troubleshooting common mistakes” and blockchain explorers. Troubleshoot in a fixed order: network, address, transaction hash, contract, then current status; in Assets & Transactions, read this specifically alongside “Troubleshooting common mistakes” and blockchain explorers. If troubleshooting looks unusual, first establish whether a transaction was actually broadcast. If “Troubleshooting common mistakes” is unclear, stop before approving and return to the basics of blockchain explorers and troubleshooting, then verify the result with a transaction hash, contract address or block record where applicable.

Good habits after the task is complete

Once the task is complete, disconnect DApps you no longer need and review approvals that may remain active; in Assets & Transactions, read this specifically alongside “Good habits after the task is complete” and troubleshooting. Keep seed phrases and private keys offline and never send them through screenshots, cloud notes, or support chats; in Assets & Transactions, read this specifically alongside “Good habits after the task is complete” and troubleshooting. Interfaces can change over time; a repeatable verification routine is more reliable than memorizing where a button used to be; in Assets & Transactions, read this specifically alongside “Good habits after the task is complete” and troubleshooting. A durable routine for Assets & Transactions is to make troubleshooting a first-pass check, use asset display as a second check, and rely on verifiable information related to token contracts rather than interface assumptions.

Security and risk reminder

Seed phrases and private keys are controlled by the user. imtoken will never ask for them. Blockchain transactions are generally irreversible by a wallet provider, and third-party DApps, smart contracts, network conditions and digital-asset prices can introduce additional risk.