How to Track a USDT TRC-20 Transaction by Hash on TronScan

To check a USDT TRC-20 transaction, copy its hash (TXID) from your wallet, paste it into the search bar on tronscan.org and open the transaction page. A transfer is done when the result is SUCCESS and the block is confirmed, which on TRON takes about a minute. The same page shows whether the token is real USDT and what the transfer cost. Below is the routine, with two real transfers from Oct 19, 2026 read field by field.

Where to find the transaction hash

The hash, also called TXID, is a 64-character string of digits and letters a to f. Wallets label it differently, so look for the idea rather than a specific word:

1. Open your transaction history and tap the USDT transfer you want to check.
2. In the details, copy the hash or ID field, or use the link that opens the transaction in a block explorer.
3. If you are the recipient, ask the sender for the hash, or search by your own address.

Sharing the hash is safe: the transfer is public anyway.

How to open the transaction in TronScan

1. Go to tronscan.org and paste the hash into the main search bar.
2. The transaction page opens. Its address has the form tronscan.org/#/transaction/<hash>, so you can also build the link yourself.
3. No hash? Search for the sender’s address. Its page lists TRC-20 token transfers, newest on top; find yours by amount and time.

If the search finds nothing right after sending, wait a few seconds: a new block is produced about every 3 seconds. The TRON transaction documentation says that by default a node drops a transaction that is not included within 60 seconds of the latest block’s timestamp. In that case the USDT stays with the sender.

How to read the status

Two things tell you whether a transfer is final: the result of the contract call and the state of the block.

The result

The result says whether the USDT contract finished the transfer. In the TRON protocol definition (Tron.proto) a successful call has the result SUCCESS. The failures you are most likely to meet with USDT are:

• OUT_OF_ENERGY: the address ran out of energy and TRX to burn, or the fee limit was too low;
• REVERT: the contract rejected the call, for example because the balance was too small;
• OUT_OF_TIME: the call took longer than the network allows.

A failed transaction is still in a block and still paid for, but no USDT moved. Why it happens with energy and how to resend without losing TRX twice is covered in the OUT OF ENERGY error guide.

Confirmed or not yet

TRON uses 27 active Super Representatives that take turns producing blocks. According to the TRON consensus documentation, a block becomes solidified, meaning irreversible, once at least 19 distinct active Super Representatives have each produced a block at that height or above. The documentation puts this at about 1 minute. Until then the transaction is pending and, in theory, could be dropped in a fork.

We checked the gap ourselves: on Oct 19, 2026 between 05:20 and 05:24 UTC, the public TronGrid node showed the latest solidified block 18 blocks behind the newest one in all three readings. At 3 seconds a block, that is 54 seconds.

The documentation advises services that credit large amounts to wait for solidification, so a deposit can appear on the recipient’s side a little later than in TronScan.

How to make sure it is real USDT

Anyone can create a TRC-20 token called USDT. The only reliable check is the contract address. Real USDT on TRON is TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t, and its token page is on TronScan.

On the transaction page, check two places:

• The contract that was called. A USDT transfer is a call to the USDT contract, so the “to” side of the raw transaction is the contract, not the person who received the money.
• The token transfer details. They show the token, the amount, the sender and the recipient. Click the token and make sure it opens the contract above.

If the contract is different, the “USDT” is a fake token, whatever the name and logo.

What the transfer cost

The resource section of the transaction page shows what the network charged. In TRON API terms, the receipt has these fields:

Field (API name)	What it means
energy_usage_total	All energy the USDT contract used
energy_usage	The part covered by energy already on the sender’s address, staked or delegated
energy_fee	TRX burned for the energy that was missing, in SUN
net_usage	Bandwidth covered by the free allowance or staked bandwidth
net_fee	TRX burned for bandwidth, in SUN
fee	Everything burned in total, in SUN

Total TRX burned = (energy_fee + net_fee) / 1,000,000. As of Oct 19, 2026 the network burns 100 SUN per unit of energy and 1,000 SUN per unit of bandwidth (chain parameters getEnergyFee and getTransactionFee). Most of the energy figure is the dynamic surcharge on the busy USDT contract, which what TRON energy is explains in detail.

Two real transfers, field by field

Both transfers are in block 87,237,974, produced on Oct 19, 2026 at 05:15:42 UTC. The data comes from the TronGrid API and the TronScan API.

Field	Transfer A	Transfer B
Amount	1,000 USDT	191.604366 USDT
Result	SUCCESS	SUCCESS
Token contract	TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t	TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t
Energy used in total	64,285	130,285
Covered by energy on the address	0	130,284 (+1 by the deployer)
TRX burned for energy	6.4285	0
Bandwidth	345, burned	345, covered
TRX burned for bandwidth	0.345	0
Total burned	6.7735 TRX	0 TRX
Fee limit set by the sender	100 TRX	30 TRX

What the two columns tell you:

• Transfer A had no energy and no spare bandwidth: 64,285 × 100 SUN plus 345 × 1,000 SUN, 6,773,500 SUN burned.
• Transfer B used twice the energy because the recipient held no USDT before it, see why sending to a new address costs more. Energy on the address covered it, so nothing was burned.
• The fee limit is a cap, not a charge. Transfer B set 30 TRX and paid 0.

What you see and what it means

What you see	What it means	What to do
SUCCESS, block confirmed	The transfer is final	If the recipient sees nothing, check the contract and address
SUCCESS, not yet confirmed	The transfer is in a block, waiting for solidification	Wait about a minute
OUT_OF_ENERGY	Not enough energy and TRX, or fee limit too low	See the OUT OF ENERGY guide
REVERT	The contract rejected the call	Check the USDT balance and the recipient address
Nothing found after a minute	Not in a block	The USDT is still on your address
Token contract is not TR7NH…Lj6t	It is not real USDT	Do not treat it as a payment
energy_fee above 0	TRX was burned for energy	Next time get energy before sending
net_fee 345,000	0.345 TRX burned for bandwidth	Normal when less than 345 of the free 600 a day are left; see bandwidth cost

A quick checklist

1. Copy the hash and open it on tronscan.org.
2. Check the result and that the block is confirmed.
3. Check the token contract and the recipient in the token transfer details.
4. Look at the resources: energy, bandwidth, TRX burned.

If the last step shows several TRX burned on every transfer, energy on the sending address would have covered that part. The current rental rate and how renting works are on the pricing page, and the ordering steps are in the guides.

FAQ

How long does a USDT TRC-20 transfer take to confirm? It lands in a block within seconds and becomes irreversible after about a minute, once 19 of the 27 Super Representatives have built on top of it. We measured a 54-second gap on Oct 19, 2026.

It shows SUCCESS, but the recipient sees nothing. Why? Check the recipient and the token contract. If both are right, the recipient’s service may be waiting for solidification.

Can I cancel a USDT transfer after sending? No. Once the transaction is in a block, only the recipient can send the USDT back.

Why is the “to” address in the transaction the USDT contract? Because a USDT transfer is a call to the token contract. The person who received the money is listed in the token transfer details.