Skip to content
Cutfee

Blog

USDT transfer failed with OUT_OF_ENERGY, or “not enough TRX”: what it burned, and the fix

Figures measured from api.cutfee.com/pub/rates, api.cutfee.com/pub/tiers. The price moves; these endpoints answer with today's.

A USDT transfer on TRON needs Energy, and a wallet without Energy pays for it in TRX. At 20:13 UTC on 27 September 2026 that meant 6.50 TRX for a transfer to an address holding USDT and 13.10 TRX to an address with none. Renting the same Energy at Cutfee cost 1.95 TRX and 3.93 TRX. If your wallet holds less TRX than it needs, one of two things happens, and they cost very different amounts.

Two different failures

The wallet warns that you do not have enough TRX for the fee, and does not send. Nothing has happened on the network. A transaction that was never broadcast costs nothing, and your USDT and TRX are where they were. The wallet has estimated the Energy, multiplied it by the network price, and found your TRX short.

The transfer was sent and Tronscan shows OUT_OF_ENERGY. The network started running the transfer and stopped when the TRX it could burn ran out. The USDT did not move. The TRX burned before it stopped is gone: the network does not refund computation that was already done.

The second is the expensive one, and it is not rare. We read every third block from 86,622,431 to 86,622,539, 37 blocks between 20:08 and 20:14 UTC on 27 September. 47 of the 1,831 calls to the USDT contract in them failed with OUT_OF_ENERGY.

What a failed transfer costs: a real one

46 of those 47 cost nothing. The sending address had no Energy and no TRX to burn, so the transfer stopped at its first instruction with 0 Energy used. Only 345 bytes of the free daily Bandwidth were spent.

The 47th is the case to avoid. Transfer 854e2c8f… had a fee limit of 60 TRX, so the limit did not stop it. The sender's TRX did. The network ran it for 46,550 Energy, which is all that the TRX left after Bandwidth could buy, and stopped at a step that writes a balance (SSTORE). The receipt:

In the receipt Value
Energy used 46,550 (a normal transfer needs 64,285)
Burned for Energy 4.655 TRX
Burned for Bandwidth 0.345 TRX
Total fee 5.00 TRX
USDT moved none

Five TRX spent and nothing sent. Retrying with the same balance would do it again. With 6.50 TRX of Energy (or 1.95 TRX of rented Energy) in place first, the same transfer would have gone through.

So a half-full wallet is worse than an empty one. If you are not sure you have enough, get the Energy first rather than letting the transfer try.

How much TRX the wallet actually wants

Recipient Energy the transfer uses Burned without Energy Plus Bandwidth, once today's free 600 bytes are used
Holds USDT 64,285 6.43 TRX about 0.35 TRX
Holds no USDT 130,285 13.03 TRX about 0.35 TRX

Our prices are for whole packages of 65,000 and 131,000 Energy, which is why this page quotes 6.50 and 13.10. Why a token transfer needs so much Energy, and how to tell in advance which of the two rows applies, is in why TRON burns TRX on a USDT transfer.

Four ways to run out, and the fix for each

1. No Energy and too little TRX. The two cases above. Fix: rent the Energy before sending: 65,000 for 1.95 TRX, or 131,000 for 3.93 TRX. Or top the wallet up to at least 6.8 TRX (13.4 TRX for a recipient without USDT) and let it burn.

2. You rented 65,000 Energy, but the recipient had no USDT. The transfer needs 130,285, so the wallet is 65,285 Energy short and burns TRX for the rest: about 6.53 TRX. If it does not have that much, you get case 1 with the rented Energy used up as well. Fix: check the recipient on Tronscan first. No USDT among its tokens means you rent 131,000 (3.93 TRX), not 65,000.

3. The Energy went to another address. Rented Energy is delegated to the address the payment came from. If you paid from an exchange, or from a second wallet, that address got the Energy, not the one holding your USDT. Fix: pay from the wallet that will send the USDT. How the delegation works, and how to see it on Tronscan.

4. The hour ran out. Rented Energy stays for one hour and is then taken back. A transfer sent after that burns TRX as if you had rented nothing. Fix: send within the hour; your address page on Tronscan shows the delegated Energy while it is there.

What we cannot fix

To rent Energy you pay at least 1.95 TRX, from the same wallet that sends the USDT. If that wallet has no TRX at all, renting does not solve the problem: first get a little TRX onto that address, from an exchange withdrawal or from someone who can send it. Then rent, then send the USDT.

Check it yourself

Today's prices, as our site shows them:

curl https://api.cutfee.com/pub/rates
curl https://api.cutfee.com/pub/tiers

The failed transfer's receipt, with result: OUT_OF_ENERGY, energy_usage_total: 46550 and energy_fee: 4655000 (in sun, so 4.655 TRX):

curl -X POST https://api.trongrid.io/wallet/gettransactioninfobyid \
  -d '{"value":"854e2c8f7a29f37a74044b24b8a514d5361e85a0c007e551269f7fe2e539726c"}'

The sample: every third block from 86,622,431 to 86,622,539, 37 blocks. One call returns the receipts of a whole block; count those sent to the USDT contract and those among them with result: OUT_OF_ENERGY. The failed transfer above is in block 86,622,467:

curl -X POST https://api.trongrid.io/wallet/gettransactioninfobyblocknum \
  -d '{"num":86622467}'

Your own failed transfer shows the same fields. On Tronscan, look at its result and at the Energy and TRX under its resources.

When you are ready to send, the price of the Energy is on the home page. What a transfer costs in general, with the price history, is in USDT TRC-20 transfer fee today.

All articles