Transaction Checks｜imtoken

Use a five-part review covering address, network, amount, contract details and transaction hash.

On this page

Before submission: address

To understand Transaction Checks, place before submission: address inside the full on-chain workflow instead of treating it as an isolated label. The practical point is to verify before submission: address in the context of the selected blockchain network. The user should compare the request with the intended address, asset, account or contract before confirming. A wallet can organize information and submit requests, but the selected network and the blockchain determine the final state. On-chain state and a transaction hash provide stronger evidence than a delayed interface alone. Third-party DApps, services and smart contracts can introduce risks that need separate review. If the interface does not match your expectation, verify the network, address, contract and on-chain record before taking another action.

A practical way to approach before submission: address is to use a consistent review sequence. First, the practical point is to verify before submission: address in the context of the selected blockchain network. Next, the user should compare the request with the intended address, asset, account or contract before confirming. After a transaction, signature or approval is submitted, on-chain state and a transaction hash provide stronger evidence than a delayed interface alone. Finally, third-party dapps, services and smart contracts can introduce risks that need separate review. This sequence gives each confirmation a clear reason and helps reduce wrong-network transfers, address mismatches, unnecessary permissions and repeated actions caused by a delayed interface.

The practical point is to verify before submission: address in the context of the selected blockchain network
The user should compare the request with the intended address, asset, account or contract before confirming
On-chain state and a transaction hash provide stronger evidence than a delayed interface alone
Third-party DApps, services and smart contracts can introduce risks that need separate review

Before submission: network and amount

To understand Transaction Checks, place before submission: network and amount inside the full on-chain workflow instead of treating it as an isolated label. The practical point is to verify before submission: network and amount in the context of the selected blockchain network. The user should compare the request with the intended address, asset, account or contract before confirming. A wallet can organize information and submit requests, but the selected network and the blockchain determine the final state. On-chain state and a transaction hash provide stronger evidence than a delayed interface alone. Third-party DApps, services and smart contracts can introduce risks that need separate review. If the interface does not match your expectation, verify the network, address, contract and on-chain record before taking another action.

A practical way to approach before submission: network and amount is to use a consistent review sequence. First, the practical point is to verify before submission: network and amount in the context of the selected blockchain network. Next, the user should compare the request with the intended address, asset, account or contract before confirming. After a transaction, signature or approval is submitted, on-chain state and a transaction hash provide stronger evidence than a delayed interface alone. Finally, third-party dapps, services and smart contracts can introduce risks that need separate review. This sequence gives each confirmation a clear reason and helps reduce wrong-network transfers, address mismatches, unnecessary permissions and repeated actions caused by a delayed interface.

The practical point is to verify before submission: network and amount in the context of the selected blockchain network
The user should compare the request with the intended address, asset, account or contract before confirming
On-chain state and a transaction hash provide stronger evidence than a delayed interface alone
Third-party DApps, services and smart contracts can introduce risks that need separate review

Extra checks for contract actions

To understand Transaction Checks, place extra checks for contract actions inside the full on-chain workflow instead of treating it as an isolated label. The practical point is to verify extra checks for contract actions in the context of the selected blockchain network. The user should compare the request with the intended address, asset, account or contract before confirming. A wallet can organize information and submit requests, but the selected network and the blockchain determine the final state. On-chain state and a transaction hash provide stronger evidence than a delayed interface alone. Third-party DApps, services and smart contracts can introduce risks that need separate review. If the interface does not match your expectation, verify the network, address, contract and on-chain record before taking another action.

A practical way to approach extra checks for contract actions is to use a consistent review sequence. First, the practical point is to verify extra checks for contract actions in the context of the selected blockchain network. Next, the user should compare the request with the intended address, asset, account or contract before confirming. After a transaction, signature or approval is submitted, on-chain state and a transaction hash provide stronger evidence than a delayed interface alone. Finally, third-party dapps, services and smart contracts can introduce risks that need separate review. This sequence gives each confirmation a clear reason and helps reduce wrong-network transfers, address mismatches, unnecessary permissions and repeated actions caused by a delayed interface.

The practical point is to verify extra checks for contract actions in the context of the selected blockchain network
The user should compare the request with the intended address, asset, account or contract before confirming
On-chain state and a transaction hash provide stronger evidence than a delayed interface alone
Third-party DApps, services and smart contracts can introduce risks that need separate review

After submission: transaction hash

To understand Transaction Checks, place after submission: transaction hash inside the full on-chain workflow instead of treating it as an isolated label. The practical point is to verify after submission: transaction hash in the context of the selected blockchain network. The user should compare the request with the intended address, asset, account or contract before confirming. A wallet can organize information and submit requests, but the selected network and the blockchain determine the final state. On-chain state and a transaction hash provide stronger evidence than a delayed interface alone. Third-party DApps, services and smart contracts can introduce risks that need separate review. If the interface does not match your expectation, verify the network, address, contract and on-chain record before taking another action.

A practical way to approach after submission: transaction hash is to use a consistent review sequence. First, the practical point is to verify after submission: transaction hash in the context of the selected blockchain network. Next, the user should compare the request with the intended address, asset, account or contract before confirming. After a transaction, signature or approval is submitted, on-chain state and a transaction hash provide stronger evidence than a delayed interface alone. Finally, third-party dapps, services and smart contracts can introduce risks that need separate review. This sequence gives each confirmation a clear reason and helps reduce wrong-network transfers, address mismatches, unnecessary permissions and repeated actions caused by a delayed interface.

The practical point is to verify after submission: transaction hash in the context of the selected blockchain network
The user should compare the request with the intended address, asset, account or contract before confirming
On-chain state and a transaction hash provide stronger evidence than a delayed interface alone
Third-party DApps, services and smart contracts can introduce risks that need separate review

Download imtoken Read FAQ →