Blog · 3 November 2026

TRON energy price: the burn rate's history and what renting costs against it

A unit of energy on TRON has two prices. One is the network's burn rate, a chain parameter that has stood at 100 sun per unit since 29 August 2025: what an account with no energy of its own pays in TRX for each unit a transaction needs. The other is what a seller asks to delegate that energy for a while instead. On 27 October 2026 we read the burn rate's full record, with its dates, from a public node, and the rental side from our own hourly history.

Two prices for one unit

The burn rate is the parameter getEnergyFee. When we read the chain's parameters on 2 and 3 September 2026 it stood at 100 sun per unit, and the record we read in October ends at the same value. At that rate a USDT transfer to an address that already holds USDT needs about 65,000 units and burns 6.5 TRX. A transfer to an address that has never held USDT needs about 131,000 units and burns 13.1 TRX. The guide to the transfer fee walks through the arithmetic.

A rental price is quoted in the same unit, sun per unit of energy, for a lease of a fixed term. Ours is one price per lease, recomputed against the market at a fixed interval of a few minutes. Renting at the burn rate or above it would save nothing, so the burn rate, and every cut to it, is the line every rental price is measured against.

The burn rate, as the chain records it

A full node answers the method getenergyprices with the parameter's whole record: one string of pairs, each a moment in milliseconds and the rate in sun that took effect at that moment. We made the call once, on 27 October 2026 at 21:23 UTC, and decoded the answer into dates.

The record opens with 100 at a timestamp of zero. That entry carries no date, so the table gives it none. After two cuts at the end of 2018 the rate held at its lowest for almost two years. Four rises between November 2020 and December 2022 took it to its highest, where it stayed for 655 days. It was halved on 19 September 2024 and cut again on 29 August 2025, to the 100 sun in force when we read it.

Every dated change falls on a six-hour mark, at 06:00, 12:00 or 18:00 UTC. The parameter read of September gives the chain's maintenance interval as 21,600,000 milliseconds, which is six hours. The network's governance decides each change, and between changes the rate does not move at all. The record has no field for the reason behind a change, and we did not read the governance proposals behind them.

Why older guides quote a bigger fee

A transfer's fee is the burn rate multiplied by the energy the transfer needs, so every row above changed what wallets showed and what guides printed. The last three rates, applied to today's two kinds of transfer:

At today's energy figures, a guide that puts a transfer to an address holding USDT at about twice 6.5 TRX is using the previous rate, and one at about four times is using the rate before it. Twice 6.5 TRX is also close to the 13.1 TRX a transfer to an address with no USDT burns today, so check which transfer a guide is pricing before dating it.

The older rows price today's transfer at those rates. What a transfer needed, and so burned, in those years has a history of its own that this read does not cover. Today's figures are measured: a USDT transfer we ran as a constant call on mainnet on 7 September 2026, with nothing broadcast, needed 64,285 units to an address holding USDT and 130,285 to an address holding none. The round 65,000 and 131,000 used across this site sit just above them.

What renting cost against it

Our side of the comparison is public. GET /v1/tariff/history?range=30d answers with 720 hourly points for one lease at a time, chosen with duration_s, and needs no key. We read it for the five-minute lease and the one-hour lease on 27 October 2026 at 21:25 UTC. Both series run from 22:00 UTC on 27 September to 21:00 UTC on 27 October.

No hour of either lease came near the burn rate. Over that month the dearest hour cost about a third of it, and the median hour a little over a fifth. The rental price also moved far more often than the network's rate: the five-minute lease changed from one hour to the next 212 times in those 720 hours. Which hours of the day were the cheap ones is a separate question, answered from the same history in when TRON energy is cheapest.

A month is as far back as this record reaches. The range parameter takes 24h, 7d or 30d, so it cannot show what rental prices did around the cut of August 2025, and we have no other measurement of that. What other sellers publish for themselves is on the market page, each rate with the moment it was read. Before setting two such rates side by side, read how to compare TRON energy providers.

Reading both prices yourself

Neither number has to be copied from a page. On any full node the burn rate is the key getEnergyFee in the answer to getchainparameters, and its history is getenergyprices; neither call signs anything. A script that prices transfers should read the rate rather than carry it as a constant, since the record above shows that constant going out of date eight times. GET /v1/tariff answers with our current price for each lease, and the pricing page shows it live with the burn cost beside it.

curl -s 'https://api.nrg.market/v1/tariff/history?range=30d&duration_s=3600'
# 720 hourly points for the one-hour lease: t, price_sun, maintenance_price_trx, custom

Chart the same thirty days for either lease yourself, with no key and no account: GET /v1/tariff/history in the API reference →