We run a TRON energy rental platform, and almost every week the same error report arrives: “Out of Energy”. It usually comes from a user who tried to send USDT, watched the transfer fail, and got in touch a few minutes later.
Two things about that moment confuse people. First, the USDT balance has not moved and nothing was sent. Second, the TRX in the wallet went down anyway. In short: the transfer did not go through, and no USDT left the wallet. The network still burned TRX to pay for the resources the contract call used.
Most users assume that a failed transaction is never charged. That is the biggest misconception. Once a wallet submits a contract transaction, the contract consumes resources as it runs, even if it fails in the end. The system burns TRX to pay for that automatically.
I wrote this guide to explain what causes the error and how to fix it. Saving your USDT here means two things: the transfer going through, and your balance not paying for failed attempts. When a transfer fails, the USDT does not disappear. It is stuck. The funds stay in your wallet address, but you cannot use them until you cover what the transfer needs.
What actually triggers the error
A USDT transfer needs two resources: bandwidth carries the transaction’s data size, and energy pays for the contract work. This error is almost always caused by running short of energy. When a contract call needs more energy than your address can supply, the network charges for the work already done, then reverts the transaction.
Even so, a transfer can usually still succeed when the wallet lacks energy. As long as the wallet holds enough TRX, the network simply burns TRX to cover the cost. Partial energy works the same way: the part you hold is spent first, the rest is paid by burning TRX, and the transfer still lands.
The error usually appears in the other case: the energy you hold, plus the TRX you allow the transaction to burn, together still fall short.
So the question to watch is how much energy the transfer needs. That depends mainly on which wallet you are sending to. The full math is in our guide to how much energy a USDT transfer needs.
- If the receiving wallet already holds USDT, the contract writes into a balance record that already exists. Budget about 65,000 energy.
- If the receiving wallet has never held USDT, the contract has to create that record first. Budget about 130,000 energy.
So the same transfer, from the same wallet, can cost twice the energy purely because the receiving address is different. The tier follows the recipient’s USDT balance at the moment you send, not how old the address is. An address can be years old and sit at a zero USDT balance. It then costs exactly the same as a brand-new one that has never transacted.
The energy a contract call needs is not fixed either. TRON applies a dynamic multiplier to busy contracts, and the USDT contract currently costs about twice its base level. The multiplier is recalculated every six hours. An energy figure copied out of a tutorial last month may already be too low today. That is the second reason the same transfer can succeed in the morning and fail at night.
One more thing worth knowing: energy is bound to the address, not to a single transaction. If a batch script or several teammates send from the same wallet, they all draw on the same pool of energy under that address. This is the fastest energy drain we have seen on TRON.
What a failure costs you
Burning TRX is what a shortfall turns into, so the number worth knowing is what the network charges for it.
Energy is priced at 100 sun per unit, and one TRX is 1,000,000 sun. The two tiers work out like this.
| Transfer | Energy | Burned if TRX covers the call |
| Recipient already holds USDT | 65,000 | 6.5 TRX |
| First-time recipient | 130,000 | 13 TRX |
A failure does not bill you these exact figures. What it consumes is everything you made available: the energy you hold, plus TRX up to the allowance you set. Nothing lands. You pay for the attempt, not for the transfer.
Burning is irreversible. Whether the transfer ends up on the chain or not, the TRX consumed is deducted from your balance and never comes back. That is the loss we want to help users avoid.
How to check your energy before you send
We check this every time, because it takes about twenty seconds.
- Open tronscan.org and paste your own T-address into the search bar. No wallet connection is needed, and no seed phrase.
- Open the Resources section on the account page. It shows Energy and Bandwidth, each with a used figure against a limit.
- Subtract used from limit. That remainder is what your next transfer can draw on.
If you script your transfers, the same numbers come from a single node call. wallet/getaccountresource returns both your account’s own figures and the network’s totals. It also accepts a plain browser request with the address in the URL.
The same check in more depth, including the usual pitfalls, is in our guide to checking your TRON energy before a USDT transfer.
How to fix it, step by step
The same list covers a transfer that has already failed and one that has not. Here is how we get it through, whether it is a one-off or part of a daily run.
- Work out which tier your transfer falls into. If you do not know whether the recipient holds USDT, size for 130,000 energy.
- Check the remaining energy on your sending address, using the method above. If you send from a script, a bot or an exchange API, also check what the transaction is allowed to burn. That setting is yours, and a limit below the full cost of the call is the classic cause of this error on an address that does hold some energy.
- Close the gap by renting TRON energy. Providers delegate it straight to your address, so you only ever share the public T-address, never a private key. If you have never rented before, our guide to renting TRON energy walks through the whole process.
- Size the rental to one transfer, not to a day. Rented energy restores over a rolling 24-hour window, so one rental covers one send. A second send in the same hour needs a fresh rental, or it burns TRX.
- If you send every day, stake TRX instead. Staking does not spend anything, and you keep the TRX. Unstaking takes about 14 days, so stake only amounts you will not need right away. At today’s network stake, one TRX staked yields about 9.6 energy a day, so covering one 65,000-energy transfer daily takes roughly 6,800 TRX, about $2,200 at today’s price. That yield is a snapshot and moves with total network stake.
- Do not trust the provider’s order page on its own. Wait until the energy shows on your address before you hit send. An order can read “filled” before the delegation is in a block.
Most delegations land within seconds. Confirming it yourself costs one page refresh.
FAQ
Can I undo an “Out of Energy” failure after it happens?
No. The transaction has already reverted, there is no refund, and the same transaction cannot be retried. What you can do is send it again with enough energy.
Does a failed transfer put my USDT at risk?
For a plain USDT transfer, no. The case where funds really can be stranded is a contract call, such as a swap or a bridge. There, an earlier step can already have gone through, and funds can end up sitting in the contract. That is why simulating a contract call before you sign matters more than sizing a plain transfer.
Does renting energy mean giving up my private key or seed phrase?
No. A delegation attaches energy to your public T-address. Any provider that asks for a key or a seed phrase is a scam.
Why did the same transfer work yesterday and fail today?
Usually the recipient. If their USDT balance went to zero since your last send, your transfer moves from the 65,000 tier to the 130,000 tier. The other cause is the six-hour multiplier on the USDT contract, which can raise the energy a transfer needs.
Can I just keep more TRX in the wallet instead?
You can, and the network will burn it at 100 sun per unit. That works, but you pay 6.5 TRX or 13 TRX on every transfer you make.
Sources
- TRON official resource documentation — how Energy and Bandwidth are consumed, the rule that available energy is spent before TRX is burned, the 24-hour recovery window, and the 14-day waiting period after an unstake request. (Official text)
- TRON chain parameters — the energy unit price of 100 sun, set by committee proposal #104 and effective 29 August 2025; 1 TRX = 1,000,000 sun. (Governance parameter)
- TRON Dynamic Energy Model — the per-contract multiplier recalculated at each maintenance interval, which is 6 hours, and the energy factor behind a busy contract’s cost. (Protocol mechanism)
- On-chain energy measurements for a USDT TRC-20 transfer — about 65,000 energy to a recipient that already holds USDT, and about 130,000 to a first-time recipient. (On-chain observation, September 2026)
- TRON network staking data — the daily energy pool and the total TRX staked for energy, from which the snapshot of about 9.6 energy per staked TRX per day is derived. (Network statistics)
- TRX reference price of about $0.33, September 2026 — used only for the USD conversion in step 5, and a market observation rather than a fixed rate. (Market observation)
- TRON transaction execution semantics — the energy a call needs is covered first from available energy and then by burning TRX up to the transaction’s fee limit; a call that exhausts both reverts, the energy consumed up to that point is charged, and an earlier transaction in a multi-step flow keeps its effect. (Protocol mechanism)
This article is educational. TRON parameters are set by network governance and can change, and TRX prices move daily, so verify current figures before you size anything. Nothing here is financial advice.