Methodology

Overview

Each tracker reads burn records from the chain itself, or from the official data provider for that chain. It checks every record against the rules for its burn mechanism and adds up the ones that pass. What counts as one record depends on the asset. For SHIB it is a single transfer, for ETH a whole block, and for TRX one day’s total from TRONSCAN.

This page covers what all trackers have in common. Each tracker also explains its own mechanisms under its data tables, down to the exact calculation, the source and the first block it covers.

One burn, step by step

The largest record on the SHIB tracker is a single transfer from 16 May 2021. This is what the tracker checked before counting it.

Four days earlier, the same wallet sent about 50.69 trillion SHIB to the India Covid-Crypto Relief Fund. That transfer went to a wallet someone controls, so it was never a burn, and the tracker doesn’t count it.

Checks

A record has to pass all four checks. If it fails one, it stays out of the total.

• Right token. The record belongs to the token’s canonical contract, or its native denomination, on the network we track.
• A real burn. The tokens went to a reviewed address no one can spend from, or the protocol destroyed them under its own rule. A treasury or exchange wallet doesn’t qualify, however long the tokens sit there.
• Exact amount. We keep the raw integer amount and convert it with the token’s own decimals. Nothing is rounded before it is added to the total.
• Final. The block or ledger is finalized, irreversible or validated. Pending records, removed logs and orphaned blocks are skipped.

When a source fails, trackers retry instead of moving on. The ETH tracker re-reads a failed window from a second, independent node and never moves past a block it couldn’t read. The LEO tracker only accepts live records that two providers agree on.

From raw amounts to totals

Chains store amounts as whole numbers in their smallest unit. ETH, for example, is recorded in wei, and 1 ETH is 10¹⁸ wei. We convert with each chain’s decimals and keep every record’s date, source and transaction or block reference. Duplicates are dropped by their unique ID, which on EVM chains is the transaction hash plus the log index.

Opening balances

Some mechanisms start from a reconciled balance, because their early history isn’t available record by record or day by day. The balance counts toward the all-time total, the burned supply and the cumulative chart. It is left out of the today, 7-day, 30-day and other dated figures, where it would look like one enormous day.

TRX also has one fixed record: the 1,000,000,000 TRX Independence Day burn on 25 June 2018, which TRONSCAN reports as a supply adjustment and which is added exactly once.

LUNC works differently. Burns we can attribute to a transfer or to the transaction tax are counted first, and a daily residual covers the rest of the supply reduction. Together, direct burns, tax burns and the residual always equal peak supply minus current supply. If supply rises on a day, the residual for that day is negative.

Figures on a tracker

All trackers calculate their figures the same way. Days are UTC calendar days.

Why peak supply? Because burns shrink today’s supply, measuring against it inflates the share. SHIB has burned 410.76T against a launch supply of 1,000T, which is 41.08%. Against today’s 589.50T it would read 69.7%, as if the burns had counted twice.

A day with no record adds nothing to a 7-day or 30-day sum. On the burn calendar that day is blank, not zero: having no record for a day doesn’t prove nothing was burned. The exception is a coin whose every source is proven for that day: either the source is checked against the on-chain balances of its burn addresses on every update and has been checked past the end of the day, or its history is complete and closed, because the chain or program that burned it can burn no more. When every source of a coin is proven for a day, that day shows as 0.

Figures on the dashboard

The dashboard adds up every tracker for one period. A period ends on the last complete UTC day: 1D is that day, 1Y is 365 days, and All starts at the first tracked burn.

Burn types group mechanisms: fee and usage burns, buyback and burn, and burn-wallet and planned burns. LUNC’s signed supply residual is not a burn type; it counts in the totals and is listed under the burn types. Opening balances count in All and in the supply baseline, never in a dated period, the chart or the pace.

Coins ranked by net supply

A few coins mint about as much as they burn. CAKE’s emission builds up at 44 CAKE per BNB Smart Chain block and is minted in weekly lumps, and PancakeSwap burns most of it within the week, so CAKE’s burns are many times larger than the fall in its supply: about 5.11 billion CAKE sent to the dead address or locked for good, against a supply that has shrunk by about 56 million since its peak. Ranking CAKE by its burns would put it far ahead of coins whose supply fell more. On the CAKE tracker, the homepage, the category pages and the dashboard, CAKE’s figures are therefore its net supply drop: for a period, its net supply at the end of the day before the period minus its net supply at the period’s last day (for All, the peak minus the latest reading), valued at each day’s price like any burn. Net supply is read after each weekly burn, and the share uses the highest such reading, 392,073,932.81 CAKE on 11 September 2023, as the peak. When more CAKE was minted than burned, the figure is negative, counts negatively in every total and is shown with a minus sign. CAKE’s transfers are not listed among the largest single burns, and CAKE sits in no burn-type card on the dashboard, because each weekly burn is mostly CAKE minted the same week. On the top-burner cards CAKE’s figure is labelled net. CAKE is left out of the homepage’s biggest increase and the dashboard’s biggest changes: its figure is CAKE burned minus CAKE newly minted, a small difference between two large amounts, so its change from one period to the next swings widely. The dashboard’s chart stacks each period’s burns upward from zero, so a day, week or month in which CAKE’s supply grew is drawn as 0; the totals and the chart’s table count it as a negative amount. The CAKE tracker still shows every gross burn, labelled as gross.

Mechanisms

28 mechanisms across 13 trackers. The date is when each mechanism’s own records begin. Anything earlier is covered by an opening balance or is outside the tracker, as noted under known limitations.

Sources

Burn records come from the chains themselves or from each chain’s official data. Market data is only used for dollar values and supply context.

Known limitations

Every tracker has gaps or boundaries. These are the ones that matter most when you read the numbers.

• ASTER. Only ASTER on BNB Smart Chain counts; ASTER bridged to Aster Chain is not included. Since 29 June 2026 the burns come from the team’s reserve, held in its multisig wallet, rather than from buybacks, so they cut effective total supply but not circulating supply.
• BNB. The gas-fee line also holds BNB that people send to the dead address; the BEP-95 gas-fee burn is not yet shown on its own. Binance’s Pioneer Burn Program credits, 146,252.71 BNB of lost coins counted as burned without a burn transaction, are left out, so our total differs from Binance’s official figure. BNB Beacon Chain has shut down, so its burns come from captured explorer records.
• CAKE. The net supply is read once a week, at each burn (daily before 15 September 2021), so it changes in weekly steps. A reading can include CAKE minted shortly before the burn and not yet burned; the next reading measures the level again. Only CAKE on BNB Smart Chain counts; bridged CAKE on other chains is not included. PancakeSwap’s burn total is 5.93 million CAKE higher than this tracker’s Burned (dead address) line, because it counts two transfers that never reached a burn address.
• ETH. The total is gross base-fee burn. It doesn’t subtract new issuance and leaves priority fees out, so on its own it can’t tell you whether ETH supply grew or shrank.
• HYPE. Assistance Fund activity before 22 March 2025 is one reconciled balance of 17,987,320.50473923 HYPE, not individual trades. HyperCore burns before 1 October 2026 are one 1,104,483.93233325 HYPE balance, because no official source splits them by day, so dated figures include HyperCore burns only from that date. HyperCore amounts for the current day appear once it closes. HYPE sent to the HyperEVM zero address is not counted separately, because priority fees, already counted as gas, land there too.
• ICP. Only complete UTC days are published, so the current day appears once it closes.
• LEO. Every LEO burn so far has been on Vaulta, and each one is checked there. No LEO has been burned on Ethereum. LEO that Bitfinex has bought back but not yet burned stays out until the burn is on chain. Bitfinex’s own burn list adds up to 2,445,529 LEO less than the chain shows, so totals built from that list come out lower than ours.
• LUNC. Anything before the post-collapse supply peak on 13 May 2022 is outside the tracker. Tax burns before 17 December 2024 can’t be attributed to the tax and sit in the reconciliation residual.
• PURR. The 400,000,000 PURR launch burn comes from Hyperliquid’s announcement, because no transaction was published; Hyperliquid’s own supply figures agree with it. Fee burns before 26 May 2025 are one 2,927,950.28804 PURR balance, because Hyperliquid’s trade archive records no fees before then, so dated figures include fee burns only from that date. From 26 May 2025 to 2 October 2026 the daily figures are the fees in that archive, which explain the measured supply change to within 0.02%. HyperCore amounts for the current day appear once it closes.
• SHIB. Only transfers to a fixed, reviewed list of burn addresses count. Tokens sent to other addresses that look like burn addresses are not included.
• TRX. Daily totals arrive after TRONSCAN’s publication delay, so the latest day can lag. Burns before 8 March 2021 are one reconciled balance.
• UNI. Only UNI on Ethereum counts. A burn started on another chain is added when its UNI reaches the dead address on Ethereum, so burns still in transit are not in the total yet.
• XRP. Ledgers 1 to 32,569 can’t be recovered. The 0.003680 XRP they account for is included in the archive’s first day. Historical transaction counts aren’t rebuilt.

Data status

Each tracker shows whether its data is current, and the status page shows the same for every mechanism and for our API.

The ETH and HyperEVM trackers continue from the last block they saved, so an outage delays records instead of losing them. A gap that can’t be filled is marked on the tracker.

Corrections

We recalculate a total when a source revises its data, a chain reorganises, a duplicate turns up, or a record turns out to belong to a different mechanism. If an article or video quoted a figure that changed, it gets a dated correction note, as set out in our editorial policy.

If you think we’ve missed a burn, or counted something that isn’t one, send the transaction hash or the official source through our contact page. We’ll check it against the rules on this page.