A USDT TRC20 transfer is in a TRON block within about 3 seconds and becomes irreversible โ 'solidified' โ after roughly one minute, once 19 of TRON's 27 Super Representatives have produced blocks on top of it. Most recipients credit it at that point; the liquidity provider behind KOT.CASH waits for 20 confirmations, which is the same minute. When a TRC20 transfer takes much longer, the delay is almost never the TRON network itself: it is a failed transaction, an exchange queue or a deposit sent to the wrong place.
Step by step: what happens in that minute
- Broadcast (0 s). Your wallet signs a call to the USDT contract and sends it to a TRON node.
- Block (โ 3 s). One of the 27 Super Representatives includes it in the next block. Tronscan shows it with the label Unconfirmed and a result: SUCCESS, or a failure such as OUT_OF_ENERGY.
- Solidified (โ 57โ60 s). After 19 more blocks by different producers, the block is solidified. Tronscan switches the label to Confirmed. Reverting it would need more than a third of the producers to collude.
- Credited. The recipient's system notices the confirmed transfer. Swap providers and exchanges usually credit within seconds to a few minutes after that.
Why some TRC20 transfers fail instead of waiting
TRON has no fee auction. A transaction either has the resources to run, or it fails. A USDT transfer needs energy: about 65,000 energy to an address that already holds USDT and about 130,000 to one that has never held it. Without staked or rented energy the network burns TRX to cover it โ around 13 or 27 TRX at October 2026 parameters. If the wallet allows a fee limit lower than that, or there is not enough TRX, the transaction ends with OUT_OF_ENERGY. It is recorded on-chain, the TRX already spent is gone, and the USDT never moved.
A failed transfer looks alarming in Tronscan but is simple to handle: top up TRX (or rent energy), then send again. The USDT TRC20 fee calculator shows how much TRX the transfer will need for your recipient.
Where the real delays come from
| Symptom | Likely cause | What to do |
|---|---|---|
| No hash at all | Exchange has not processed the withdrawal yet | Check the withdrawal status; exchanges batch or review |
| Hash exists, result FAILED | Out of energy or fee limit too low | Add TRX or energy, send again |
| Confirmed, not credited | Wrong deposit address or old order | Compare the address with the deposit page |
| Confirmed, wrong network | Recipient expected ERC20 or BEP20 | Contact the recipient's support with the hash |
Exchange withdrawals deserve their own mention. Many exchanges send TRC20 withdrawals within minutes, but large ones may queue them, run risk checks, or pause TRON withdrawals during wallet maintenance. Until the exchange broadcasts the transaction, there is nothing on Tronscan to look at โ the article on exchange withdrawals stuck in pending covers those cases.
Checking a transfer on Tronscan
Paste the hash into Tronscan. The page shows Result (SUCCESS or the error), the status label (Unconfirmed or Confirmed), the block number, and under Token Transfers the USDT amount and the from/to addresses. Look at the token transfer line, not the top-level 'To' field: for a TRC20 transfer that field shows the USDT contract TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t, not the recipient. The transaction hash identifier helps if you are not sure which network a hash belongs to.
Sending at busy times
TRON's throughput is high enough that ordinary congestion does not delay USDT transfers the way gas spikes delay Ethereum. What changes during busy periods is the price of energy on rental markets, not the speed of inclusion. One real exception is a period of TRON node or RPC trouble on the wallet side: if your wallet cannot reach a node, the transaction is never broadcast. Switching the wallet's node or simply retrying a minute later solves it. Each TRON transaction also carries an expiration time โ typically 60 seconds after signing in most wallets โ so a transaction that was signed but not broadcast in time is rejected rather than queued.
How it compares with other USDT networks
TRC20 sits in the middle. USDT on BNB Smart Chain confirms in under a minute too (the provider waits for 60 blocks of under a second each). USDT ERC20 needs 6 Ethereum blocks โ about 72 seconds โ but costs more gas. USDT on Solana is in a block in under a second and the provider waits for 200 confirmations, under two minutes. The choice between networks is rarely about speed; it is about the fee and what the recipient accepts, as the guide on the best network for USDT explains.
FAQ
How long does a USDT TRC20 transfer take?
About 3 seconds to be in a block and about a minute to be solidified (Confirmed on Tronscan).
Why does Tronscan say Unconfirmed?
The block has not yet been built on by 19 Super Representatives. It changes to Confirmed after about a minute.
What does OUT_OF_ENERGY mean?
The transfer failed because it did not have enough energy or TRX to pay for it. The USDT did not move; add TRX or energy and send again.
How many confirmations does a TRC20 deposit need?
The provider behind KOT.CASH waits for 20, about a minute. Exchanges set their own number, usually similar.
My exchange shows the withdrawal as processing for an hour. Is TRON slow?
No. Until the exchange broadcasts it there is no TRON transaction; the delay is on the exchange's side.