How to check a USDT TRC-20 transaction on Tronscan
How to find your USDT TRC-20 transaction hash, read each field on Tronscan, spot fake USDT, and know what to send support when something does not match.
Published by Minevana · October 14, 2026 · 10 min read
The short answer
To check a USDT TRC-20 transaction, copy its 64-character transaction hash from your exchange or wallet, paste it into the search box on tronscan.org and confirm four things: Result shows Success and Status shows CONFIRMED, the token is Tether USD from contract TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t, the receiving address matches the one you meant to pay in full, and the amount is what you sent.
Where do I find my transaction hash?
The transaction hash, also called the TxID or transaction ID, is created when a transfer is broadcast to the network. On Tron it is 64 characters long, made of the digits 0 to 9 and the letters a to f, with no 0x in front. Where to find it depends on where you sent from:
- Binance: open your withdrawal history. On the website, hover over the wallet icon, then go to Overview, Orders, Assets History and Withdraw. While the status says Processing, wait; once it says Completed, click the TxID to see the transaction details. The app's menus differ and change between versions, so look for your withdrawal or transaction history there.
- Other exchanges: open the withdrawal in your withdrawal or asset history and look for a field called TxID, Transaction ID, Tx hash or Hash.
- Trust Wallet: open your transaction history, tap the transfer, then tap the option to view it on a block explorer. The explorer page shows the hash. The button's wording can differ between app versions.
- Other self-custody wallets, such as TronLink: open the transfer in the activity or history list. Most show the hash with a copy icon, or a link that opens it on Tronscan.
- The TxID says [Internal]: Binance says a transfer between Binance accounts creates no TxID; the TxID field shows [Internal] and you get an internal transfer ID instead. Nothing appears on Tronscan, so keep that ID: it is what Binance support asks for.
- The TxID is blank, or the status says Processing: the exchange has not finished sending, so there is nothing on Tronscan yet. Wait and refresh.
How do I check a USDT TRC-20 transaction on Tronscan, step by step?
- 1
Open tronscan.org yourself
Type tronscan.org into your browser or use a bookmark, because look-alike explorer domains exist. Looking a transaction up needs no account, no wallet connection and no seed phrase, so ignore any prompt to connect a wallet.
- 2
Paste the whole hash into the search box
Paste the full 64-character hash into the search bar at the top and press Enter. One missing character and Tronscan finds nothing. If it still finds nothing, see the table on pending and failed transfers below.
- 3
Check Result and Status first
Result should say Success. Status should say CONFIRMED. A transfer that is only seconds old can show UNCONFIRMED; on Tron that normally changes within about a minute.
- 4
Read the token transfer, not the top-level contract
A USDT transfer is a call to the USDT token contract, so the transaction's contract address is the token contract, not the person who was paid. The real movement is listed in the TRC-20 transfer section of the page, with its own from, to and amount.
- 5
Confirm it is real USDT
The token should read Tether USD (USDT), and its contract must be exactly TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t. Click the token name to open its page and compare. Any other contract is not Tether's USDT, whatever it is called.
- 6
Compare the receiving address in full
The "to" address in the token transfer must match the address you meant to pay, all 34 characters, not just the first and last few. Tron addresses start with T.
- 7
Compare the amount, then save the record
USDT on Tron has six decimals, so 25 USDT can appear as 25 or 25.000000. Any dollar figure shown beside it is an estimate Tronscan adds, not part of the transaction. Save the page link, which contains the hash, and a screenshot.
What does each field on Tronscan mean?
A USDT TRC-20 transaction page on Tronscan carries these fields. What to check in each:
| Field | What it means | What to check |
|---|---|---|
| Hash | The unique ID of this transaction, 64 characters. | The same hash as in your exchange or wallet. |
| Result | Whether the contract call ran: Success, or a failure code such as REVERT or OUT_OF_ENERGY. | Success. Anything else means no USDT moved. |
| Status | CONFIRMED once its block is final (solidified), UNCONFIRMED before that. | CONFIRMED. |
| Block and time | The block that included the transaction, and when it was produced. | A time that fits when the transfer was sent. Check whether it is shown in UTC or your local time. |
| Owner address (from) | The account that signed the transaction. For a plain transfer, the sender. | Your address, or your exchange's sending wallet if you withdrew from an exchange. |
| Contract address | The contract the transaction called. For USDT, the token contract. | TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t. |
| TRC-20 transfer: to | The address that received the tokens. | The address you meant to pay, all 34 characters. |
| TRC-20 transfer: token and amount | Which token moved, and how much. | Tether USD (USDT), and the amount you sent. |
| Resources consumed and fee | The energy and bandwidth the sender used, and any TRX burned to pay for them. The fee limit is the most the sender allowed, not what was paid. | Nothing to match. The sender paid it, in TRX or with staked or rented resources; it does not come out of the USDT amount. |
Tronscan updates its layout from time to time, so a label can read slightly differently; the information is the same.
How do I tell real USDT from a fake token?
Anyone can create a Tron token, call it USDT or Tether USD and copy the logo. The name proves nothing. The contract address does.
- One contract is real. Tether's own list of supported protocols, on tether.to, gives TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t as USDT on Tron. A token from any other contract is not Tether's USDT.
- Check it on the transaction itself. Click the token in the TRC-20 transfer section and compare the contract on its page with the one above, every character.
- Treat Tronscan's ratings as a hint, not proof. Tronscan gives tokens a reputation rating and keeps ones it rates Suspicious or Unsafe out of its search, but a rating is Tronscan's own judgement. The contract address is what counts.
- Ignore tokens you did not ask for. Some dust campaigns airdrop tokens whose names carry phishing links, or put scam messages in the memo. Do not visit the link, and do not sign or approve anything to claim or unlock a token.
- Watch for address poisoning. Scammers send tiny transfers from addresses that copy the first and last characters of one you use, hoping you later copy theirs from your history. Copy a payment address from where it was given to you, never from your transaction list, and compare it in full.
- Make sure it is on Tron at all. USDT sent on Ethereum or BNB Smart Chain will not show on Tronscan. Their hashes and addresses start with 0x; Tron addresses start with T.
What does pending, unconfirmed or failed mean?
| What you see | What it means | What to do |
|---|---|---|
| Exchange shows Processing, or no TxID yet | The exchange has not broadcast the transfer. Nothing is on the blockchain. | Wait, and ask the exchange if it does not change. |
| Wallet shows Pending | Sent to the network but not yet in a block. Tron adds a block about every three seconds, so this is usually brief. | Wait a few minutes, then search the hash on Tronscan. |
| Tronscan finds nothing | The hash is incomplete, it belongs to another network, or the transfer never made it into a block. | Copy the full hash again and check the network. If it is still not there, no USDT moved on Tron. |
| Status: UNCONFIRMED | It is in a block, but that block is not final yet. | Refresh after about a minute. |
| Result: REVERT or failed | The USDT contract refused the transfer, for example because the sender did not hold enough USDT. No USDT moved, but the sender may still have paid for the energy used. | Do not count it. The sender has to make a new transfer. |
| Result: OUT_OF_ENERGY | The transfer ran out of energy before it finished, because the fee limit or the TRX balance was too low. No USDT moved, and the energy or TRX already used is still charged. | A new transfer is needed, with enough TRX or energy. |
| Success and CONFIRMED, but not credited | The transfer is complete on-chain. The receiver's own system has not caught up. | Send the receiver the hash and wait for their check. |
How much is the fee for a USDT TRC-20 transfer?
Tron has no flat fee. A USDT transfer uses two resources: bandwidth, for the size of the transaction, and energy, for running the USDT contract. A sender who has staked or rented these uses them; otherwise Tron burns TRX from the sender's balance to pay. Either way the sender pays, and it is not taken from the USDT sent.
A snapshot, true on 11 October 2026 and certain to change: two USDT transfers on Tron that day used 64,285 energy when the receiving address already held USDT and 130,285 energy when it held none, plus 345 bandwidth each. The energy burn price was 100 sun (0.0001 TRX) per unit, still the value on 13 October 2026, so paying entirely by burning TRX would have cost about 6.4 TRX or about 13 TRX: roughly $2.10 or $4.30 with TRX near $0.33 that day. Each account gets 600 free bandwidth over a rolling 24 hours; once that is used, the 345 bandwidth costs another 0.345 TRX.
These numbers move. The energy and bandwidth prices are network parameters that can be changed by proposal, Tron's dynamic energy model charges more energy for heavily used contracts such as USDT, and the TRX price changes daily. An exchange also sets its own withdrawal fee. On Binance, for example, if you enter a withdrawal amount rather than a receive amount, the fee comes out of it and the receiver gets less than you typed.
What should I send support if the amount or address does not match?
First rule out the common causes: an incomplete hash, the wrong network, an exchange fee taken out of the amount, or a transfer that is still unconfirmed. If it still does not match, send the receiver one message with everything needed to trace it. For a payment to Minevana, that goes through the support page:
- The full transaction hash or the Tronscan link. For an internal exchange transfer, the internal transfer ID.
- The network and token: Tron (TRC-20), USDT.
- The amount you meant to send and the amount Tronscan shows.
- The address you were given and the address the transfer went to, both in full.
- The address you sent from, and the exchange or wallet you used.
- The date and time you sent it, with your time zone, and the email on your account.
- Screenshots of the Tronscan page and of your exchange or wallet record.
- Never your seed phrase, private key, password or a login code. No support team needs them.