How to Verify a USDT Transaction Hash
This guide explains how to verify whether a transaction hash actually involves the official USDT contract on TRC20, ERC20, or BEP20. The most important step is checking the correct network and comparing the transaction with the official Tether contract for that network.
Open Transaction Verifier
Official Contract Addresses
What a transaction verification really means
Transaction verification is not just about confirming that a transfer exists. It is about checking whether the transaction involves the official USDT contract on the selected network, rather than a lookalike or unrelated token.
Step-by-step: verify a USDT transaction hash
- Select the correct network — TRC20, ERC20, or BEP20.
- Paste the transaction hash.
- Run the transaction verifier.
- Review the result including amount, sender, recipient, and explorer link.
- Confirm the official contract match.
- Review public risk information where available.
Official USDT contract addresses used for transaction checks
| Network |
Official USDT contract |
| TRC20 |
TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t |
| ERC20 |
0xdAC17F958D2ee523a2206206994597C13D831ec7 |
| BEP20 |
0x55d398326f99059fF775485246999027B3197955 |
What USDTCheck.app helps with
- Checks whether the transaction involves the official USDT contract for the selected network.
- Shows amount, sender, recipient, network, and explorer links.
- Shows public risk information where available from the configured source.
- Makes explorer-style verification easier for non-technical users.
Public risk information for transactions
Some transaction checks may show public warning or risk signals. For example, a transaction or one of the involved addresses may have a public cautionary signal from the configured source.
Important: A result that says No public risk tag found is not a guarantee of safety. It only means the configured public source did not show such a warning at that time.
Common mistakes when checking transaction hashes
- Choosing the wrong network.
- Trusting the transaction screenshot instead of the actual explorer data.
- Ignoring the token contract involved in the transfer.
- Assuming a public warning is the only factor that matters.