Start with the network. Once you know where the transfer happened, check whether the wallet balance or transfer is tied to the USDT or USDT0 identifier expected on that chain. USDTCheck currently covers TRON, Ethereum, BNB Smart Chain, Polygon, Arbitrum One, Plasma, Avalanche C-Chain, Solana and TON.
Open USDTCheck.app USDT Contract ReferencesMany users assume that if a token is called “USDT” or “Tether,” it must be genuine. That is where mistakes happen. A token name, logo, or screenshot is not enough. A fake or misleading token can look real to a non-technical user, especially if somebody is trying to rush a payment or create pressure.
That is why verification matters. You need to know whether the result you are looking at actually points to the network-specific USDT contract reference on the correct blockchain.
The name alone is never the final check. The core question is:
Does this wallet balance or transaction involve the USDT contract reference for the selected network?
If the answer is yes, that is a strong positive sign. If the contract address is different, then the asset does not match the USDT contract reference used for that network, even if the token name looks familiar.
USDT exists on multiple networks. On USDTCheck.app, the supported networks are:
This first step is critical. If you verify a transaction or wallet on the wrong network, the result will be misleading. Many mistakes happen because users mix up networks and assume all USDT is the same everywhere.
You can verify USDT in two main ways:
Both checks are useful. A wallet check helps you inspect holdings. A transaction check helps you confirm whether a specific transfer is related to genuine USDT.
Important: “USDT contract reference” does not mean every entry below has the same issuance model. TRON, Ethereum and Avalanche C-Chain use Tether-published USD₮ contracts. Solana uses Tether's USD₮ mint and TON uses Tether's USD₮ Jetton master. BNB Smart Chain is classified as the BNB Chain USDT-6D8 / BSC representation used by the checker. Polygon, Arbitrum One and Plasma use USDT0 contract references.
This is the most important step when you verify USDT. The result should match the network-specific contract reference for the chosen network.
| Network | USDT contract reference |
|---|---|
| TRC20 | TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t |
| ERC20 | 0xdAC17F958D2ee523a2206206994597C13D831ec7 |
| Avalanche C-Chain / ERC20 | 0x9702230A8Ea53601f5cD2dc00fDBc13d4dF4A8c7 |
| Solana / SPL USD₮ mint | Es9vMFrzaCERmJfrF4H2FYD4KCoNkY11McCe8BenwNYB |
| TON / USD₮ Jetton master | EQCxE6mUtQJKFnGfaROTKOt1lZbDiiX1kCixRv7Nw2Id_sDs |
| BEP20 | 0x55d398326f99059fF775485246999027B3197955 |
| Polygon / USDT0 | 0xc2132D05D31c914a87C6611C10748AEb04B58e8F |
| Arbitrum One / USDT0 | 0xFd086bC7CD5C481DCC9C85ebE478A1C0b69FCbb9 |
| Plasma / USDT0 | 0xB8CE59FC3717ada4C02eaDF9682A9e934F625ebb |
If the contract involved is different, then you are not looking at the USDT contract reference for that chain.
After a check, you should look at the explorer link and the key details shown in the result. For transaction checks, that usually includes:
For wallet checks, look at the network and the USDT balance result. The goal is not just to see that something exists, but to understand whether it matches the network-specific contract reference and makes sense in context.
Some checks may also show public risk information. This can be useful when a public source has identified warning signals such as phishing, scam-related labels, blacklist flags, or similar cautionary indicators.
Important: “No public risk tag found” does not guarantee safety. It only means the configured public source did not show a warning at the time of checking.
Risk information should be treated as an additional signal, not as the only decision-making factor. The first and most important step is still checking the network-specific contract reference match.
For TRC20 verification, select Tron and compare the result with the official TRC20 contract:
TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t
TRC20 is one of the most commonly used USDT networks. It is popular because many users choose it for fast transfers and practical day-to-day use. Because it is so widely used, it is also important to verify that the contract matches exactly and not just assume the displayed token is real.
For ERC20 verification, select Ethereum and compare the result with:
0xdAC17F958D2ee523a2206206994597C13D831ec7
On Ethereum, users often see many 0x-format addresses and token pages. That can be confusing for non-technical users. The safest rule remains the same: do not trust the token name alone. Compare the contract involved with the USDT contract reference.
For BEP20 verification, select BNB Smart Chain and compare the result with:
0x55d398326f99059fF775485246999027B3197955
On BEP20, the contract match remains the primary authenticity check. USDTCheck may also show BscScan public warning context where available, but an explorer warning result is separate from the token-contract comparison. If the contract does not match the BNB Smart Chain reference used by the checker, do not assume the token is the BSC USDT representation you intended to inspect.
Select the correct chain and compare the result with that network’s USDT0 contract reference. The checker pages below explain the exact reference used on each network:
Most verification mistakes happen because users skip one of these basics.
If someone is comfortable with the relevant blockchain explorer, they can inspect the wallet or transaction and compare the contract address themselves. USDTCheck.app simply makes that public-data check easier to follow for people who do not routinely use explorer pages.
Yes. USDTCheck.app is a read-only checker. It does not require wallet connection, seed phrases, private keys, or token approvals.
The fastest way is to select the correct network, run a wallet or transaction check, and compare the result with the network-specific contract reference for that network.
Then it is not the USDT contract reference for that network, even if the name looks familiar.
No. A contract match is a strong and important check, but users should still review the transaction context, explorer details, and any public warnings available.
Yes. Risk warnings may be related to addresses or transaction history, not only the token contract itself.
BNB Smart Chain accuracy note: USDTCheck uses 0x55d398326f99059fF775485246999027B3197955 for BEP20 checks. BNB Chain identifies this as USDT-6D8 / a BSC USDT representation. Tether’s current supported-protocol page does not list this address as a native BNB Smart Chain USD₮ contract.
If you use USDT but are not sure why the contract address matters, read our plain-English guide. It explains why a familiar token name or logo is not enough and what USDTCheck actually compares.
USDT Contract Addresses ExplainedIf you want to verify USDT safely, the process should always come back to the same core rule: identify the correct network, compare the result with the network-specific contract reference, and review the explorer details instead of trusting names or screenshots alone.