How the UNI burn total is calculated
UNI has no burn function, so a UNI burn is a transfer to an address from which no one can ever spend it. The total adds up the UNI in every finalized transfer on Ethereum, since UNI’s genesis, into three reviewed addresses.
The dead address is shown as Burned. The UNI token contract and 0x…0001 are shown as Permanently locked. On every update, the running total for each address is checked against that address’s on-chain UNI balance.
Which UNI burns are counted
Burned (dead address)
Burned is the sum of the UNI in finalized Transfer logs of the canonical UNI contract (0x1f9840a8…4201F984) into 0x…dEaD. It includes the 100,000,000 UNI UNIfication burn (governance proposal 93, 27 December 2025) and every protocol fee burn that has reached Ethereum.
0x…dEaD is the standard burn address. No one is known to hold its key, and its UNI balance has always equalled the UNI sent to it, so none has ever left.
The history from genesis block 10,861,674 is a fixed set of Ethereum logs up to a cutoff, and their sum equals the address’s on-chain balance at that cutoff. Each update adds its new logs to a running total, and stops without moving on if that total differs from the dead address’s balance.
A burn started on another chain counts only when its UNI arrives at this address on Ethereum, so it is never counted twice.
Permanently locked
Locked is the sum of the UNI in finalized Transfer logs of the canonical UNI contract into the UNI token contract itself and into 0x…0001.
The UNI contract has no function that can move its own balance, and a contract can’t sign the permit that would let it approve a transfer. 0x…0001 is the address of a built-in Ethereum function (a precompile). It has no code that can move tokens, and no one is known to hold a key for it.
Like the dead address, each has always held exactly the UNI sent to it, so none has ever left, and both are checked against their balances on every update.
What the record covers
Coverage starts at the UNI genesis mint, block 10,861,674 on 14 September 2020. The supply baseline is the 1,000,000,000 UNI genesis supply.
Uniswap governance can mint up to 2% of supply a year, but none has been minted since genesis. Every update checks the supply and stops if any has been.
What is not counted
- Zero-value transfers, which move nothing.
- Transfers to 0x0, which the UNI contract rejects.
- UNI held in any other contract.
- Bridged UNI on other chains.
- Burns started on another chain that have not yet reached Ethereum.
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. |