How the SHIB burn total is calculated
A SHIB burn is a transfer of SHIB to a place it can never leave. The total adds up every such transfer on Ethereum into a fixed, reviewed set of four destinations.
Which SHIB burns are counted
Dead-wallet and contract-burn transfers
The tracker reads the ERC-20 Transfer logs of the canonical SHIB contract in finalized Ethereum blocks. It adds up the SHIB in every transfer whose destination is the zero address, the standard dead address, the Vitalik Buterin SHIB dead address, or the SHIB token contract’s burn balance.
Each log is counted once, by its transaction hash and log index. The three destinations other than the zero address were checked to confirm that no SHIB has ever been sent out of them. The total of all counted transfers is reconciled to SHIB’s genesis supply minus its current totalSupply, plus the balances held at the destinations.
What the record covers
Coverage starts when SHIB was deployed, at Ethereum block 10,569,013 on 31 July 2020.
What is not counted
- Transfers to any address outside the four reviewed destinations.
- Transfers of tokens from any contract other than the SHIB contract.
- Logs that were removed from the chain, and logs in blocks that are not yet finalized.
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. |