Sending USDT on TRON calls the token's A program recorded on a blockchain. It performs defined actions with funds and data when called, such as exchanging tokens according to an application’s rules.. That call consumes Energy, while the transaction itself consumes Bandwidth. These are network resources. If the sender cannot cover them with available resources, TRON burns TRX, its native coin, to pay the charge. An ordinary USDT balance does not pay this charge automatically.
That gives you three different numbers: USDT transferred, resources consumed, and TRX burned. A fourth number—the withdrawal fee charged by an exchange—belongs to the exchange's service. It need not match the network charge.
Read the receipt before interpreting the fee
Open the transaction hash in TRONSCAN. The token transfer, transaction result, resource usage and fee answer different questions.
| Receipt field | What it tells you |
|---|---|
| Result / SUCCESS | Whether execution succeeded; check the USDT Transfer event for the token movement |
Energy Usage / energy_usage_total |
Total Energy consumed by execution |
energy_usage |
Energy supplied from the caller's resources; it does not identify own staking versus delegation |
energy_fee |
TRX burned for Energy, recorded in sun |
net_usage |
Bandwidth supplied as a resource |
net_fee |
TRX burned for Bandwidth, recorded in sun |
Fee / fee |
Total transaction fee in sun; reconcile its components |
| Fee Limit | Maximum caller-side Energy budget, not the amount actually charged |
One TRX equals 1,000,000 sun. Energy usage is a count of resources, so 64,285 Energy does not mean 64,285 TRX. A receipt can show substantial resource use and little or no TRX burn.
Resources can come from staking or incoming delegation. If resources cover the call, Energy is still consumed, even when the receipt records no Energy burn. Their acquisition may have a separate cost.
Example 1: Energy burned, Bandwidth covered
A 10,060 USDT transfer on 18 April 2026 at 09:39:06 UTC succeeded in block 81,945,791. Its public Mainnet receipt records:
- 64,285 Energy consumed;
- 6,428,500 sun burned for Energy: 6.4285 TRX;
- 345 Bandwidth supplied as a resource, with no Bandwidth burn;
- total fee: 6.4285 TRX.
The network price histories confirm the applicable prices on both example dates: 100 sun per Energy and 1,000 sun per Bandwidth. Dividing 6,428,500 sun by 64,285 Energy independently reproduces the Energy price in this receipt. The explorer's 30 TRX Fee Limit is a budget, not the paid fee. The receipt also records 49,635 energy_penalty_total; those units are already part of the 64,285 total and must not be added again.
Example 2: Energy covered, Bandwidth burned
An 843 USDT transfer on 9 October 2026 at 04:11:48 UTC succeeded in block 86,948,776. It consumed the same 64,285 Energy, all supplied as a resource. No Energy burn was recorded. Its Bandwidth fee and total fee were both 345,000 sun, or 0.345 TRX.
At the applicable 1,000-sun Bandwidth price, 345,000 ÷ 1,000 gives 345 billed Bandwidth. The receipt establishes resource coverage, but does not establish whether the sender staked TRX or received delegated Energy. It also does not disclose a rental payment made elsewhere.
A successful TRON transaction and an exchange credit are separate stages. If the deposit is missing, follow the guide to a completed withdrawal with no deposit.
Why the next transfer can cost a different amount
Energy executes the USDT contract. Bandwidth covers transaction size. The amount of USDT alone does not determine either charge: contract execution, storage state and TRON's dynamic Energy model affect the resources required. The two receipts above do not establish a universal 64,285-Energy transfer. A recipient with no USDT balance can involve a different contract-storage path; that is separate from whether the TRON account has been activated. Zero USDT balance does not mean an unactivated account.
Mainnet parameters read on 15 October 2026: burning pays 100 sun per Energy and 1,000 sun per Bandwidth. The per-account free Bandwidth cap is 600. These are dated network parameters, rather than a permanent transfer tariff.
Energy can be partly covered by resources and partly by TRX burn. Suppose a call needs 64,285 Energy, the sender has 50,000 available, and the contract deployer contributes none:
(64,285 − 50,000) × 100 ÷ 1,000,000 = 1.4285 TRX burned for Energy.
Bandwidth follows a different rule for an ordinary transaction: TRON first tries to cover the whole transaction from staked or incoming delegated Bandwidth, then from free Bandwidth, provided both the account’s remaining free quota and the network’s shared free quota cover it. If neither source can cover it, it burns TRX for the whole Bandwidth charge. You cannot combine 200 staked Bandwidth and 145 free Bandwidth to cover a 345-Bandwidth transaction.
For an explicitly hypothetical 345-Bandwidth transaction with no qualifying coverage, that adds 345 × 1,000 ÷ 1,000,000 = 0.345 TRX, making the conditional total 1.7735 TRX. This is an illustration using the dated parameters, not another observed transfer or a wallet quote.
Resources recover progressively over a 24-hour window. They do not reset at midnight, and the 600 free cap does not guarantee a free transfer every day. A token transfer still needs Energy even when its Bandwidth is covered.
Choose how to cover the resources
| Route | When it fits | What determines the cost |
|---|---|---|
| Burn liquid TRX | An ordinary wallet has enough TRX and you want a direct occasional transfer | Actual execution, available resources and network prices |
| Stake your own TRX | Repeated transfers justify keeping capital staked | Your share of network staking, resource type and capital committed |
| Receive delegation or buy a rental | Someone supplies resources to the ordinary sending address | Amount, delivery, validity, rental payment and any remaining burns |
| Use a supported token-paid wallet flow | The wallet and provider support the specific flow and token | The provider's displayed token fee and any activation charge |
Staking and delegation
Staking TRX allocates Energy or Bandwidth. It does not buy a fixed lifetime quantity: the allocation depends on your share of the network's stake. The current Stake 2.0 unstaking waiting period is 14 days, so staking for a single transfer also commits capital for longer than that transfer takes.
With delegation, another account keeps its staked TRX and voting rights, while your address receives resource rights. Commercial rental adds a payment arrangement to that network mechanism. Receiving delegation itself does not require your seed phrase, private key, a USDT spending approval or a change to your account permissions.
Compare the rental quote with the burn it would actually avoid, including remaining Energy burn, Bandwidth burn and the rental payment. Enough Energy alone does not guarantee zero TRX burn. Delivery must reach the address that sends the USDT before it sends; the usable amount and validity matter. An unlocked delegation can be revoked.
That distinction also matters for exchange withdrawals: resources delegated to your receiving wallet do not automatically reduce the exchange's withdrawal tariff.
Paying in USDT through a wallet
TronLink's documented GasFree flow uses a separate GasFree wallet. You sign an authorisation, a provider submits the transaction, and the supported token pays the provider's charge. The first transfer can include an activation charge alongside the transfer fee, displayed in the interface.
This does not make contract execution free or make every ordinary TRON address able to send USDT without TRX. It is a specific wallet/provider payment route. A quoted USDT charge belongs to that flow; it is not the network's universal USDT transfer price.
Withdrawing from an exchange
For an exchange withdrawal, the exchange controls the sending wallet and sets the withdrawal fee. Its debit from your exchange balance and the amount you receive describe the service transaction. The blockchain receipt describes the sender's network transaction. They need not have the same amount or currency, so a 0.345 TRX network fee does not establish what the customer paid the exchange.
What Fee Limit protects—and what it does not
Fee Limit caps the caller-side Energy budget, including available Energy resources. It is neither an instruction to spend that amount nor a cap on Bandwidth charges. If the call runs out of Energy, the USDT transfer can fail while resources are still consumed. Repeatedly retrying with the same insufficient budget can therefore add costs.
The useful reading order is: result and token movement → Energy used and burned → Bandwidth used or burned → total fee. For a rental or token-paid route, add the separate provider payment to understand your full cost.
For the broader wallet, application and account context, see the TRON ecosystem guide.
Sources
Network rules: Resource Model, Paying for Resources, Bandwidth and Energy, Delegation. Wallet flow: TronLink GasFree user guide. Historical network prices: Energy prices, Bandwidth prices. Mainnet parameters and public receipts were read on 15 October 2026; transaction dates are given beside each example.