A plain USDT transfer on TRON consumed 64,285 energy and 345 bytes of bandwidth in the block we sampled this morning. At the network's current rates that is 6.4285 TRX of energy plus 0.345 TRX of bandwidth — 6.7735 TRX burned by a sender holding neither — and every number in that sentence is on chain, in a receipt, checkable in about a minute.

The two parameters that decide the bill

TRON prices resources with chain parameters that super representatives vote on. Two of them set what you burn. Ask the chain directly:

curl -s https://api.trongrid.io/wallet/getchainparameters \
  | python -c "import json,sys; print({p['key']:p.get('value') for p in json.load(sys.stdin)['chainParameter']})"

Three keys matter here. getEnergyFee is 100 — SUN burned per unit of energy. getTransactionFee is 1,000 — SUN burned per byte of bandwidth. getFreeNetLimit is 600 — bandwidth every account gets free each day. One TRX is 1,000,000 SUN, so TRON's own documentation states the same rates as 0.0001 TRX per energy and 0.001 TRX per byte.

getEnergyFee has read 100 since TRON proposal #104 was approved on 29 August 2025, cutting it from 210. That single parameter is why every article still quoting about 13.6 TRX for a USDT transfer is a year out of date.

A real transfer, receipt and all

You do not have to take the arithmetic on trust. Pull recent transactions of the USDT TRC20 contract from TronGrid, then read any one of them back with gettransactioninfobyid. In block 86000888 (6 September 2026, 06:00:12 UTC), transaction fa63f49d…2e3b came back with:

"energy_usage_total": 64285,
"energy_fee":         6428500,
"net_fee":            345000,
"fee":                6773500

Now redo it yourself. 64,285 × 100 = 6,428,500 SUN of energy. 345 × 1,000 = 345,000 SUN of bandwidth. Add them: 6,773,500 SUN, which is the fee field, which is 6.7735 TRX. The chain parameters, the receipt and a calculator all agree. Paste the hash into any block explorer and you will get the same figures.

Why 64,285 and not 14,650

The same receipt carries a field most fee guides never mention: energy_penalty_total, and for this transfer it reads 49,635. More than three quarters of the energy that transfer paid for was a penalty, not the contract's base cost.

TRON runs a dynamic energy model. A contract that burns more than a threshold of energy inside a maintenance period — six hours, per getMaintenanceTimeInterval — has its energy cost multiplied, and the multiplier ratchets up while the contract stays busy. The cap is getDynamicEnergyMaxFactor, currently 34,000 on a precision of 10,000, so at most 4.4× base cost.

Ask the chain what USDT is paying:

curl -s -X POST https://api.trongrid.io/wallet/getcontractinfo \
  -d '{"value":"41a614f803b6fd780986a42c78ec9c7f77e6ded13c"}'

It returns "energy_factor": 34000 — exactly the network maximum. Tether's contract is so heavily used that TRON is charging the full 4.4× for touching it. That, more than the price of energy itself, is why renting energy is a business at all: strip the penalty out and a transfer would need under 15,000 energy.

The other size

In the same block, transaction 69255e8d…3e92 used 130,285 energy for the same kind of call. That is a transfer into an address with no USDT balance entry yet, so the contract has to create one. Roughly double, which is where the board's second column comes from — and why it is a different transaction rather than a safety margin, as we set out separately.

Bandwidth: the half nobody rents

Energy gets the attention; bandwidth quietly costs money too. The transfers we looked at were 345 bytes. Against a free daily allowance of 600 bandwidth, that means your first transfer of the day is usually free on this line and your second one is not — it burns 345,000 SUN, about a third of a TRX. Our sample shows both cases side by side in one block: some senders paid a net_fee, some did not.

Renting energy does nothing about this. Not one of the nineteen platforms we track is tagged as selling bandwidth on our compare page. You cover it by staking a modest amount of TRX for bandwidth, or by burning the third of a TRX and forgetting about it.

What renting actually changes

Energy is the line worth attacking, because it is roughly twenty times the bandwidth line. Against the 6.4285 TRX this morning's transfer burned, the cheapest hourly rental of 65,000 energy on the board right now is 1.30 TRX at NETTS, and the average across the platforms quoting that cell is 2.86 TRX. The bandwidth line is identical either way.

One detail to keep straight: the board's column is labelled 65k, and the transaction used 64,285. Platforms sell round amounts, so you are buying a little headroom, not a different product. Rent under what the transaction needs and the shortfall goes back to being burned at 100 SUN a unit.

Check it again before you trust it

Every figure above was read on 6 September 2026, and every one of them is a chain parameter or a receipt that can change. getEnergyFee changes by proposal. The dynamic energy factor is recalculated every six hours. The two commands on this page take a minute to run, and they will always beat an article — including this one.