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
Home / Transaction Checks
Step-by-step guide

Transaction Checks

Transaction Checks can become confusing when a wallet shows several networks, assets, or requests in one interface. Verify the destination address before submission. At the same time, confirm the sending network matches what the recipient supports. The practical consequence of check the asset name together with its contract address is that visual familiarity is not enough; a user needs a repeatable method for checking source, target, network, and final state.

Before you begin
  • Use a trusted device and network
  • Confirm the active account and network
  • Read the full request before signing
On this pageBefore you begin: Verify the destination address before submissionFirst execution stage: Check the asset name together with its contract addressSecond execution stage: Keep enough native asset for network feesVerify the result: Use a block explorer for the correct networkCommon mistakes and recovery: For a failed transaction, inspect the failure reason rather than only the balance
01

Before you begin: Verify the destination address before submission

Focus on confirm the sending network matches what the recipient supports

First, in Transaction Checks, the Before you begin: Verify the destination address before submission stage should not be reduced to the next button. Verify the destination address before submission. Confirm the sending network matches what the recipient supports. For Transaction Checks, the user should perform an independent review after submission, then reread the account, network, address, asset, amount, and request summary in the order they will matter on-chain. The goal is to be able to explain what will happen, on which network, and to which target before approval. That discipline is more durable than memorizing where a control appears in one version of an interface.

First follow-up in Transaction Checks: after the action described by Focus on confirm the sending network matches what the recipient supports, a success message should not be the only evidence used. Check the asset name together with its contract address. Confirm the amount and decimal display. Keep the public identifiers needed for later review, such as the transaction hash, network, and target address, and verify them through the matching block explorer or wallet record. Remember to use contract addresses as a strong identity check. If the result differs from the expectation, establish what has already happened on-chain before attempting another signature or transfer, because a second submission may create a separate action rather than repair the first one.

  • Confirm verify the destination address before submission.
  • Check how confirm the sending network matches what the recipient supports affects the current request.
  • Use check the asset name together with its contract address as a separate verification point.
02

First execution stage: Check the asset name together with its contract address

Focus on confirm the amount and decimal display

Second, in Transaction Checks, the First execution stage: Check the asset name together with its contract address stage should not be reduced to the next button. Check the asset name together with its contract address. Confirm the amount and decimal display. For Transaction Checks, the user should separate interface cues from verifiable chain state, then reread the account, network, address, asset, amount, and request summary in the order they will matter on-chain. The goal is to be able to explain what will happen, on which network, and to which target before approval. That discipline is more durable than memorizing where a control appears in one version of an interface.

Second follow-up in Transaction Checks: after the action described by Focus on confirm the amount and decimal display, a success message should not be the only evidence used. Keep enough native asset for network fees. Save the transaction hash after submission. Keep the public identifiers needed for later review, such as the transaction hash, network, and target address, and verify them through the matching block explorer or wallet record. Remember to make every step answer the question: what am I authorizing?. If the result differs from the expectation, establish what has already happened on-chain before attempting another signature or transfer, because a second submission may create a separate action rather than repair the first one.

  • Confirm check the asset name together with its contract address.
  • Check how confirm the amount and decimal display affects the current request.
  • Use keep enough native asset for network fees as a separate verification point.
03

Second execution stage: Keep enough native asset for network fees

Focus on save the transaction hash after submission

Third, in Transaction Checks, the Second execution stage: Keep enough native asset for network fees stage should not be reduced to the next button. Keep enough native asset for network fees. Save the transaction hash after submission. For Transaction Checks, the user should put public evidence ahead of visual familiarity, then reread the account, network, address, asset, amount, and request summary in the order they will matter on-chain. The goal is to be able to explain what will happen, on which network, and to which target before approval. That discipline is more durable than memorizing where a control appears in one version of an interface.

Third follow-up in Transaction Checks: after the action described by Focus on save the transaction hash after submission, a success message should not be the only evidence used. Use a block explorer for the correct network. Avoid resending blindly while confirmation is pending. Keep the public identifiers needed for later review, such as the transaction hash, network, and target address, and verify them through the matching block explorer or wallet record. Remember to start by identifying the active network. If the result differs from the expectation, establish what has already happened on-chain before attempting another signature or transfer, because a second submission may create a separate action rather than repair the first one.

  • Confirm keep enough native asset for network fees.
  • Check how save the transaction hash after submission affects the current request.
  • Use use a block explorer for the correct network as a separate verification point.
04

Verify the result: Use a block explorer for the correct network

Focus on avoid resending blindly while confirmation is pending

Fourth, in Transaction Checks, the Verify the result: Use a block explorer for the correct network stage should not be reduced to the next button. Use a block explorer for the correct network. Avoid resending blindly while confirmation is pending. For Transaction Checks, the user should confirm the object, then the action, then the result, then reread the account, network, address, asset, amount, and request summary in the order they will matter on-chain. The goal is to be able to explain what will happen, on which network, and to which target before approval. That discipline is more durable than memorizing where a control appears in one version of an interface.

Fourth follow-up in Transaction Checks: after the action described by Focus on avoid resending blindly while confirmation is pending, a success message should not be the only evidence used. For a failed transaction, inspect the failure reason rather than only the balance. If the address or network does not match, stop before signing. Keep the public identifiers needed for later review, such as the transaction hash, network, and target address, and verify them through the matching block explorer or wallet record. Remember to do not let a familiar label replace a technical check. If the result differs from the expectation, establish what has already happened on-chain before attempting another signature or transfer, because a second submission may create a separate action rather than repair the first one.

  • Confirm use a block explorer for the correct network.
  • Check how avoid resending blindly while confirmation is pending affects the current request.
  • Use for a failed transaction, inspect the failure reason rather than only the balance as a separate verification point.
05

Common mistakes and recovery: For a failed transaction, inspect the failure reason rather than only the balance

Focus on if the address or network does not match, stop before signing

Fifth, in Transaction Checks, the Common mistakes and recovery: For a failed transaction, inspect the failure reason rather than only the balance stage should not be reduced to the next button. For a failed transaction, inspect the failure reason rather than only the balance. If the address or network does not match, stop before signing. For Transaction Checks, the user should split a request into source, target, permission, and outcome, then reread the account, network, address, asset, amount, and request summary in the order they will matter on-chain. The goal is to be able to explain what will happen, on which network, and to which target before approval. That discipline is more durable than memorizing where a control appears in one version of an interface.

Fifth follow-up in Transaction Checks: after the action described by Focus on if the address or network does not match, stop before signing, a success message should not be the only evidence used. Verify the destination address before submission. Confirm the sending network matches what the recipient supports. Keep the public identifiers needed for later review, such as the transaction hash, network, and target address, and verify them through the matching block explorer or wallet record. Remember to stop when two pieces of context disagree. If the result differs from the expectation, establish what has already happened on-chain before attempting another signature or transfer, because a second submission may create a separate action rather than repair the first one.

  • Confirm for a failed transaction, inspect the failure reason rather than only the balance.
  • Check how if the address or network does not match, stop before signing affects the current request.
  • Use verify the destination address before submission as a separate verification point.

Practical checklist

  • Review verify the destination address before submission.
  • Review check the asset name together with its contract address.
  • Review keep enough native asset for network fees.
  • Review use a block explorer for the correct network.
  • Review for a failed transaction, inspect the failure reason rather than only the balance.

Continue learning

Send & Receive Gas & Confirmations Support