Why did my TRON transaction fail? Paste the TxID
Most failed USDT transfers on TRON end with OUT_OF_ENERGY: the transfer needed more energy than the sender had and the fee limit stopped it, after TRX was already burned. The rest are REVERT, when the token contract refuses the call, or transactions that were never broadcast because there was no bandwidth.
Paste the transaction hash or its Tronscan link below to see the result code, the cause, the fix and what the transaction cost.
TRON result codes and what to do
| Code | What happened | Fix |
|---|---|---|
| OUT_OF_ENERGY | Not enough energy and the fee limit or TRX balance ran out | Rent energy to the sender, or raise the fee limit |
| REVERT | The contract refused the call (e.g. not enough USDT) | Check the balance and the amount |
| OUT_OF_TIME | The call ran past the network's time limit | Retry; a heavy contract is the cause |
| Not on chain | Never broadcast, usually no bandwidth | Keep about 0.35 TRX on the sender |
| SUCCESS with TRX burned | It went through, but burned TRX for energy | Rent energy before the next transfer |
Result codes as returned by TRON nodes (gettransactionbyid). 2026-10-01.
Why the burned TRX is not returned
TRON charges for the work a transaction does, even when it fails. When a transfer runs out of energy halfway, the TRX burned for the energy it used is gone; only renting or staking energy before sending avoids it.
FAQ
Does the checker need my wallet?
No. It reads public transaction data from a TRON node in your browser; it cannot move or sign anything.
Can a failed transfer send the USDT anyway?
No. A failed transaction changes no balances except the TRX burned for fees.
Will rented energy fix a REVERT?
No. REVERT means the contract refused the call; energy only pays for the work. Check the token balance and the amount instead.