tronorb.com
Learn

Why Did My TRON Transaction Fail? Every Error Explained

OUT_OF_ENERGY, REVERT, bandwidth, insufficient balance, inactive account, expired transaction: how to read a failed TRON transaction on TRONSCAN, what it cost you, and how to fix each cause.

Updated 3 min readTronOrb team

On this page
  1. 1Find the reason
  2. 2The errors in more detail
  3. 3Does a failed transaction cost money?
  4. 4Failed vs not found
  5. 5How to avoid failed transactions
  6. 6Quick answers

A failed TRON transaction always has a reason written on-chain — or, if it never reached the chain, a clear reason on your side. Find it on TRONSCAN and you'll know exactly what to fix. This guide covers every common error, what each one costs, and how to avoid it next time.

Find the reason

Search your transaction ID on TRONSCAN and look at the status and result. Wallets often show a shorter message; TRONSCAN shows the exact one.

Result What happened Fix
OUT_OF_ENERGY Not enough energy / TRX (or fee limit too low) to finish the contract. More TRX, rent or stake energy. Details
Bandwidth / "account resource insufficient" No free bandwidth left and no TRX to burn. Add a little TRX or wait for free bandwidth. Details
REVERT The contract refused the call — e.g. not enough token balance, a frozen (blacklisted) address, or a dApp rule. Check balances and the USDT blacklist.
"balance is not sufficient" Not enough TRX for the amount plus fees. Lower the amount or top up.
Account not activated The sending address has never received TRX. Activate it.
Transaction expired It wasn't broadcast in time (signed too long ago or network issue). Create and send a new one.

The errors in more detail

OUT_OF_ENERGY

The most common error for USDT transfers. The contract needed more energy than your account had plus the TRX it was allowed to burn. Often caused by sending to an address that has never held USDT — that needs about twice the energy. Full guide.

REVERT

The smart contract itself said no. For USDT this usually means:

  • you tried to send more USDT than you have;
  • the sender or recipient is on Tether's blacklist;
  • for dApps: slippage too low, a deadline passed, or another rule of the dApp.

REVERT costs the energy used up to the point of failure.

Bandwidth errors

Every transaction needs bandwidth. Activated accounts get 600 free per day; beyond that, TRX is burned. With zero TRX and no free bandwidth left, the wallet can't even submit the transaction. Full guide.

Insufficient balance

For TRX transfers: amount + fees > balance. Leave a small TRX buffer for fees.

Account not activated

A new address that has only received USDT has no on-chain account and can't pay for anything. Send it TRX first. Full guide.

Does a failed transaction cost money?

Often yes. Energy and bandwidth used up to the failure are paid for — by burning TRX if you had no resources. The tokens you tried to send don't move. Nobody refunds the fee: the network did the work.

Errors caught before broadcasting (insufficient balance, not activated) cost nothing — the transaction never reached the chain.

Failed vs not found

If TRONSCAN shows nothing for your ID, the transaction was never broadcast — it didn't fail on-chain. See USDT transfer stuck or pending.

How to avoid failed transactions

  • Keep a TRX buffer on every address you send from.
  • Assume the first USDT transfer to a new address costs about double.
  • Check the recipient with our address check before large transfers.
  • For dApps, read the error in your wallet before retrying — repeating a REVERT just burns more TRX.

Quick answers

Can I get the fee back? No.

Why did it fail if the wallet showed the fee? Wallet estimates can be wrong, especially for new recipients or busy dApps.

Is a failed transaction visible to others? Yes, everything on TRON is public — it just shows as failed.

Related

More in Learn