How the TRX burn total is calculated
TRON destroys the resource fees that transactions pay. The TRX total adds up those fee burns since mainnet launch, and one separate burn: the 1,000,000,000 TRX Independence Day burn of 25 June 2018.
The early history is not available transaction by transaction. It is part of the lifetime total as reconciled balances, which are not shown as individual transactions.
Which TRX burns are counted
Network resource fee burns
The lifetime figure is built from three sources, one after the other in time:
- Mainnet launch through 28 December 2019: one reconciled opening balance.
- From 29 December 2019: TRONSCAN’s finalized total_burn value for each UTC day, for every day strictly before the day the tracker switched to reading blocks itself.
- From that switch, at a UTC midnight: the burn in each block, read from the chain.
The opening balance comes from the protocol’s black-hole account. Before Proposal 54 (7 March 2021), burned fees were credited to that account. Its balance, plus the fees burned directly for the rest of 7 March, is 496,769,505.704914 TRX. TRONSCAN’s daily totals cover 366,534,352 TRX of it from 29 December 2019. The remaining 130,235,153.704914 TRX, from mainnet launch through 28 December 2019, has no public daily source and is the opening balance.
The historical daily rows come from the official TRONSCAN turnover series, after its publication delay. The live rows are read from a TRON node (walletsolidity/getblock and gettransactioninfobyblocknum), with exact integer fees, a complete matching set of receipts, the block’s identity and its link to the parent block. A retained four-block sample reconciles exactly to the finalized getburntrx counter. Live records are totals per block, not individual transactions.
The previous UTC day can stay pending until TRONSCAN publishes its daily total after 02:00 UTC, even while blocks of the current day are already shown.
The switch date and the last imported daily date are stored separately. A late daily row from before the switch can be added once, but no daily row at or after it is imported. No new opening balance or signed adjustment is introduced.
Independence Day burn
The one-time supply burn of 1,000,000,000 TRX on 25 June 2018 is reported separately and added exactly once.
It is a verified supply-adjustment record from TRONSCAN. It is not a fee total and not an individual on-chain transaction.
What the record covers
The two reconciled records take coverage back to TRON’s mainnet launch.
Opening balances count in the all-time total and in the cumulative history. They are left out of the today, 7-day and 30-day figures, so they can’t appear as a one-day burn spike.
What is not counted
- The packingFee part of each fee, which is paid to the fee pool.
How the figures on this page are calculated
Every tracker works out its figures the same way. Days are UTC calendar days.
| Figure | How it is calculated |
|---|---|
| Total burned | Every accepted daily amount of every mechanism, from the date that mechanism’s coverage starts. A record counts only once it is final: a finalized burn record, or a finalized daily figure from the chain’s official data provider. Duplicates and records held back for review stay out. |
| Today, 7-day and 30-day burn | Burns are added up by UTC calendar day. Today is the current UTC day. The 7-day and 30-day figures add the current day and the 6 or 29 days before it. A day with no record adds zero, and opening balances are left out. |
| Daily and moving averages | The 7-day and 30-day averages on the cards divide those totals by 7 and 30. The average lines on the charts are plain averages of the last 7, 30, 90 or 365 daily rows, or of as many as there are. |
| Daily USD estimate | The day’s burn × the last CoinGecko USD price stored on that same UTC day. It is shown with ≈ and rounded. It is left out when no price was stored that day, and on cumulative-chart points that include an opening balance, because that balance built up before the date shown. It is a reference value: not the price at the time of each burn, not a volume-weighted price, and not sale proceeds or an exact trade value. The figure for the current UTC day can still change as burns and prices arrive. |
| Burned supply | Total burned ÷ the all-time peak supply × 100. That baseline is not the latest circulating supply, and it comes from a different source than the market data. |
| Mechanism and contributor shares | A mechanism’s amount ÷ the total burn on record, or a known contributor’s amount ÷ that total. Burns with no known sender stay in the total and are not assigned to anyone. |
| Cumulative chart | For the range you select, the chart starts at the all-time total minus the days in the range, then adds each UTC day back in order. The change over the range is the last value minus the first. |
| Burn calendar | A cell is the sum of all mechanisms for that day. Its colour ranks the day against the others, by relative size or by percentile, and never changes the amount. A day with no record is blank, which means unknown. The exception is a tracker whose every mechanism proves the day, in one of two ways. Either the mechanism holds every transfer into its burn addresses, or their exact balances, from the start of its coverage, checks them against the on-chain balances on each update, and has checked past the end of that UTC day. Or its history is complete and closed, because the chain or program that burned can burn no more. On those trackers a day with no burn shows as 0. |
| Time to burn another 10% | (Latest reported total supply × 10%) ÷ the selected daily burn pace ÷ 365.25, in years. It is a straight-line scenario, not a forecast: it assumes supply policy, issuance, activity and burn rate all stay as they are. |