One Formula, Fully Shown
Burned TRX = Energy × 0.0001 TRX/Energy — every arithmetic step is shown on this page
Short answer: Burned TRX = Energy consumed × the Energy unit price (100 sun = 0.0001 TRX per Energy). A USDT TRC-20 transfer to a recipient who already holds USDT consumes about 64,285 Energy (≈ ~6.4 TRX burned); a cold address consumes about 130,285 Energy (≈ ~13 TRX), plus about 350 Bandwidth.
Rent Energy NowOne formula: Burned TRX = Energy × unit price
TRON Energy Fee Methodology: How USDT Transfer Costs Are Calculated. This is EOPEN’s canonical fact-source page — the formula, hot vs cold consumption, worked examples and the data source, all step by step.
Burned TRX = Energy × 0.0001 TRX/Energy — every arithmetic step is shown on this page
Every figure is anchored to the TRON Resource Model / getEnergyFee and checkable on TronScan
Fees, packs and savings all come from one shared model, e.g. the 100 sun/Energy protocol parameter
EOPEN delegates resources to your own address — never touching keys, seed phrases or token approvals
For a USDT TRC-20 transfer, TRON charges "Energy consumed × the Energy unit price." That unit price is set by the protocol parameter getEnergyFee, currently 100 sun = 0.0001 TRX per Energy. A recipient that already holds USDT (a hot address) consumes about 64,285 Energy, or roughly ~6.4 TRX; a cold address that has never held USDT consumes about 130,285 Energy, or roughly ~13 TRX. Each transfer also needs about 350 Bandwidth.
Data source: TRON Resource Model / getEnergyFee (current Energy unit price 100 sun/Energy). Every conversion on this page is anchored to that official protocol parameter: hot ≈ 64,285 Energy (≈ ~6.4 TRX), cold ≈ 130,285 Energy (≈ ~13 TRX), plus about 350 Bandwidth.
Last reviewed: 2026-05-28. The final cost is always whatever the chain charges at execution time plus the live order quote.
When an account has not prepared enough Energy, TRON burns (destroys) TRX from the account at the current unit price to pay for execution. Written as a formula, with the numbers substituted in step by step:
getEnergyFee = 100 sun / Energy
1 TRX = 1,000,000 sun → 100 ÷ 1,000,000 = 0.0001 TRX / Energy
Burned TRX = Energy × 0.0001
Plug in the actual Energy consumed and you get the burn cost: hot 64,285 × 0.0001 ≈ ~6.4 TRX; cold 130,285 × 0.0001 ≈ ~13 TRX.
Calling a TRC-20 contract's transfer method consumes both Energy (execution) and about 350 Bandwidth (data). The Energy consumed depends mostly on how much storage the contract has to write:
~64,285 Energy
The recipient already has a USDT balance, so the transfer only updates an existing storage slot — lower Energy, roughly ~6.4 TRX. Rent 65,000 to leave a safe buffer.
~130,285 Energy
Sending USDT to a brand-new address forces the contract to create a new storage slot; that extra write nearly doubles Energy, to roughly ~13 TRX. Rent 131,000.
That is why "cold ≈ 2× hot": the gap comes entirely from the cost of writing storage for the first time, not from the amount sent or network congestion.
The table compares total cost of burning TRX directly versus renting through EOPEN (using the typical per-transfer rental price).
| Transfers | Burn TRX | EOPEN rental (approx) | Saved |
|---|---|---|---|
| 1 | ~6.4 TRX | ~1.5 TRX | ~4.9 TRX |
| 100 | ~640 TRX | ~150 TRX | ~490 TRX |
| 10,000 | ~64,000 TRX | ~15,000 TRX | ~49,000 TRX |
| Transfers | Burn TRX | EOPEN rental (approx) | Saved |
|---|---|---|---|
| 1 | ~13 TRX | ~3.5 TRX | ~9.5 TRX |
| 100 | ~1,300 TRX | ~350 TRX | ~950 TRX |
| 10,000 | ~130,000 TRX | ~35,000 TRX | ~95,000 TRX |
Burn cost is derived from "Energy × 0.0001 TRX"; the rental column uses the typical per-transfer price (hot 1.5 TRX / cold 3.5 TRX). Overall that is up to 80% cheaper than burning.
The figures here reflect the current mainstream model, but three classes of factors can move the real numbers:
Treat this page as the methodology and an order-of-magnitude reference. The final cost is always whatever the chain charges at execution time plus the live order quote.
The formula is "Burned TRX = Energy consumed × Energy unit price." The unit price is set by the TRON protocol parameter getEnergyFee, currently 100 sun/Energy; since 1 TRX = 1,000,000 sun, each Energy unit equals 0.0001 TRX. A hot address: about 64,285 Energy × 0.0001 ≈ ~6.4 TRX; a cold address: about 130,285 Energy × 0.0001 ≈ ~13 TRX.
When the recipient already holds USDT (hot), the transfer only updates an existing storage slot. A cold address (one that has never held USDT) requires the contract to create a brand-new storage slot on first receipt, and that extra storage write substantially raises Energy consumption — nearly doubling the total.
Every TRON transaction consumes two resources at once: Energy (compute/execution) and Bandwidth (the transaction's byte size). A USDT TRC-20 transfer needs about 350 Bandwidth on top of Energy. The "burned TRX" in this methodology refers to the Energy portion; Bandwidth shortfalls are covered separately by an account's free allowance or a small amount of TRX.
Three things: (1) whether the recipient already holds USDT, which decides hot vs cold; (2) the token contract’s current state/parameters, which shift actual consumption; and (3) on-chain TRON governance changes to the Energy unit price (getEnergyFee). The final cost is always whatever the chain charges at execution time plus the live order quote.
Without prepared Energy, the chain burns TRX at the getEnergyFee rate: about ~6.4 TRX for a hot address and ~13 TRX for a cold one. Renting through EOPEN typically costs only 1-2 TRX (hot) or 3-4 TRX (cold) per transfer — up to 80% cheaper than burning.
EOPEN uses non-custodial delegation: it delegates Energy/Bandwidth to your own TRON address and never needs your private keys, seed phrase or token approvals. Delegations are publicly verifiable on TronScan. EOPEN never DMs users first and never asks for keys or approvals.