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.
Home / Transaction Checks
imtoken

Transaction Checks

Transaction Checks: practical guidance with network, transaction, permission and security checks.

Before you begin

Transaction concepts

For Transaction Checks, this section connects Transaction concepts with Transaction workflow. Before starting, confirm the active account, network and destination, then prepare the address, amount or contract information you expect to see. Never type a seed phrase, private key, recovery phrase or verification code into an unfamiliar site.

In practical use, Transaction verification should not be evaluated separately from Transaction risk. During the flow, treat connecting, signing, approving and sending as separate actions. Read each request in context, and cancel anything you cannot interpret until the source and purpose are clear.

Treat Transaction management as part of a repeatable review routine. After the action, review transaction history or the correct block explorer and remove connections or approvals you no longer need. If something looks wrong, stop additional signatures or transfers first. This helps turn visible information into verified information.

Complete the flow step by step

Transaction workflow

For Transaction Checks, this section connects Transaction workflow with Transaction verification. Before starting, confirm the active account, network and destination, then prepare the address, amount or contract information you expect to see. Never type a seed phrase, private key, recovery phrase or verification code into an unfamiliar site.

In practical use, Transaction risk should not be evaluated separately from Transaction management. During the flow, treat connecting, signing, approving and sending as separate actions. Read each request in context, and cancel anything you cannot interpret until the source and purpose are clear.

Treat Transaction concepts as part of a repeatable review routine. After the action, review transaction history or the correct block explorer and remove connections or approvals you no longer need. If something looks wrong, stop additional signatures or transfers first. This helps turn visible information into verified information.

Common mistakes and troubleshooting

Transaction verification

For Transaction Checks, this section connects Transaction verification with Transaction risk. Before starting, confirm the active account, network and destination, then prepare the address, amount or contract information you expect to see. Never type a seed phrase, private key, recovery phrase or verification code into an unfamiliar site.

In practical use, Transaction management should not be evaluated separately from Transaction concepts. During the flow, treat connecting, signing, approving and sending as separate actions. Read each request in context, and cancel anything you cannot interpret until the source and purpose are clear.

Treat Transaction workflow as part of a repeatable review routine. After the action, review transaction history or the correct block explorer and remove connections or approvals you no longer need. If something looks wrong, stop additional signatures or transfers first. This helps turn visible information into verified information.

Post-action review

Transaction risk

For Transaction Checks, this section connects Transaction risk with Transaction management. Before starting, confirm the active account, network and destination, then prepare the address, amount or contract information you expect to see. Never type a seed phrase, private key, recovery phrase or verification code into an unfamiliar site.

In practical use, Transaction concepts should not be evaluated separately from Transaction workflow. During the flow, treat connecting, signing, approving and sending as separate actions. Read each request in context, and cancel anything you cannot interpret until the source and purpose are clear.

Treat Transaction verification as part of a repeatable review routine. After the action, review transaction history or the correct block explorer and remove connections or approvals you no longer need. If something looks wrong, stop additional signatures or transfers first. This helps turn visible information into verified information.

Risk note

Third-party DApps and smart contracts can introduce risk. Review permissions and remove approvals you no longer need.