How TRON charges energy and bandwidth for a TRC-20 transfer
Every TRC-20 transfer on TRON uses two resources, bandwidth and energy. They are billed separately, come from separate pools and refill in different ways. Bandwidth pays for the bytes of the transaction you broadcast; energy pays for running the contract code in the TRON Virtual Machine. A plain TRX transfer needs only bandwidth. A TRC-20 transfer calls the token contract's transfer(address,uint256) function, so it needs both, and the interaction between the two is where costs either stay manageable or get out of hand.
Bandwidth
Every account gets 600 free bandwidth a day, reset at 00:00 UTC. A standard TRC-20 transfer is about 345 bytes, and the network charges 1 bandwidth per byte of transaction data, signatures and memo included, so the transfer takes roughly 345 bandwidth.
If the free allowance or TRX staked for bandwidth covers that, this half of the transfer costs nothing. If the bandwidth pool is empty, the network burns TRX from the sending address at 0.001 TRX per bandwidth unit (1,000 SUN per byte): 0.345 TRX for a 345-unit transaction, no staking required. Low-volume senders rarely pay for bandwidth at all. High-volume senders usually stake TRX for it rather than burn, because a staked TRX covers more transactions than a burned one.
Energy, where the real cost is
A USDT TRC-20 transfer takes about 65,000 energy. That is the price of the bytecode the TRON Virtual Machine executes: reads and writes to the contract's balance mapping, the Transfer event, and the contract's own checks. The exact figure moves a little depending on whether a storage slot is written for the first time (cold) or updated (warm), but 65,000 is the standard number for a transfer between two addresses that both hold USDT. If the recipient's USDT balance is zero, the contract allocates a new storage slot and the cost roughly doubles, to around 130,000 energy.
Energy comes from your own staked TRX or from energy another account delegates to you. Staking gives you a share of the network's total energy pool in proportion to your stake, and used energy regenerates linearly back to 100% over 24 hours. How much energy one staked TRX yields depends on how much TRX the whole network has staked, and that shifts over time. Producing 65,000 energy a day from your own stake alone takes a lot of locked TRX, which is why energy rental exists.
If a transaction needs 65,000 energy and your account has less, the network does not run part of it. It looks at the transaction's fee_limit, burns TRX from your account up to that limit to cover the shortfall, and executes the whole transaction. If the shortfall would cost more than the fee_limit allows, the transaction fails before any state change is committed. That is the case to avoid: paying for burned TRX on top of your stake, or failing outright because fee_limit was set too low. The pricing page shows what covering 65,000 energy costs in TRX right now.
Stake 2.0 separated staking from delegation
Before Stake 2.0 went live on mainnet in April 2023, staking and delegation were one action: the owner called freezeBalance with a receiver address, and the frozen TRX was bound to that receiver. That was too rigid for a resource market.
Stake 2.0 added freezeBalanceV2 and split the two steps. You stake TRX into your own energy or bandwidth pool, then delegate the resource with a separate delegateResource call. As a result:
- A delegation can be revoked and reassigned without unstaking. The optional
lockflag holds it for at least the network's minimum lock period, currently 3 days; without the flag the delegator can pull it back at any time. - The 14-day unfreeze wait applies to the staked TRX when you withdraw it, not to the delegation.
- A rental platform can rotate delegations from one staked position across many recipient addresses.
When tronenergyrent.com delegates energy to your address, the delegated stake appears in your account state as acquired_delegated_frozenV2_balance_for_energy in wallet/getaccount. The energy counts toward your account's limit at once, and you do nothing to start using it.
Renting vs. burning
Rental is priced by duration: 1 hour, 1 day, 3 days or 30 days. The 1-hour tier is the cheapest in absolute TRX and the 30-day tier the most expensive, with 1 day and 3 days in between, because the price reflects how long the platform's TRX stays locked to your address. The per-tier prices are on the pricing page.
For anyone who plans ahead, renting almost always beats burning. Burning 65,000 energy at the network's dynamic rate is simple, but you pay whatever the burn price is at that moment, and it moves sharply when network-wide energy demand shifts. Renting fixes the TRX price when you order.
During execution the VM takes energy in a fixed order:
- From your account's limit, where your own staked TRX and the energy delegated to you by other accounts count as one combined pool
- From TRX burned from your account for any remaining shortfall, capped by
fee_limit
Rented energy simply raises your limit; there is no order between rented and own staked energy. When the rental ends and the delegation is reclaimed, the limit shrinks back to your own stake, and anything beyond it is paid by burning TRX.
Bandwidth is taken in this order: staked bandwidth (your own and delegated), then the free daily allocation, then TRX burn. Resources do not substitute for each other; spare energy cannot cover a bandwidth shortfall.
Reading your account's resources on-chain
wallet/getaccountresource returns the fields that matter:
EnergyLimit: the total energy available to your accountEnergyUsed: energy spent in the current 24-hour windowTotalEnergyLimit: network-wide total energy, useful for working out the stake-to-energy ratioTotalEnergyWeight: network-wide total staked weight for energyfreeNetLimit: your free daily bandwidth, normally 600NetLimit: bandwidth from your own staked TRXNetUsed: bandwidth spent todayTotalNetLimit,TotalNetWeight: the network-wide bandwidth totals
To see how much energy others have delegated to you, read acquired_delegated_frozenV2_balance_for_energy from wallet/getaccount. wallet/getdelegatedresourcev2 gives the detail per delegator, including any lock expiry.
If your system sends TRC-20 transfers programmatically, poll these endpoints before broadcasting and you will catch a low-energy account before it costs you an unexpected TRX burn. The API docs cover resource checks and energy orders in automated workflows.
Other TRC-20 tokens cost different amounts
The 65,000 figure is specific to the Tether contract at TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t. A token with more logic per transfer, such as fee-on-transfer mechanics, allowance checks for routers or events with several topics, uses more energy per call; a minimal ERC-20-style contract can come in under 30,000. The only reliable way to know is to simulate the transaction or look at past executions of that contract on a block explorer. Do not apply the USDT number to every TRC-20 token.