How the BNB burn total is calculated
BNB has existed on three chains, and this total counts every BNB that was provably destroyed, or sent where no one can ever spend it, on each of them.
BNB moved off Ethereum in 2019 and BNB Beacon Chain has shut down, so those two records are fixed. The BNB Smart Chain lines still grow, and on every update they are checked against the on-chain balances of the dead address and the zero address.
Which BNB burns are counted
Burns before BNB Smart Chain
On Ethereum, 2017 to 2019. The BNB in 30 successful burn() calls on the ERC-20 BNB contract (0xB8c77482…631bDD52), from 18 October 2017 to 16 April 2019. They are the seven quarterly burns (#1 to #7) and 23 smaller burns by Binance addresses and other holders, 38.76 BNB in total.
On BNB Beacon Chain, 2019 to 2024. The BNB in 22 successful burn transactions from 28 April 2019 to 17 January 2024. They are the 19 quarterly burns (#8 to #26) and three test burns of 1, 1 and 0.1 BNB.
Two kinds of burn from these years are left out. The first is the 11,654,397 BNB burned on Beacon Chain on 28 April 2019. Beacon Chain was issued with the full 200,000,000 BNB, so that burn mirrored, as a whole number, the 11,654,397.76 BNB already burned on Ethereum, and counting it as well would count the same BNB twice. The second is the burns on Ethereum from 23 April 2019 on. They retired ERC-20 BNB as it was swapped for BNB on Beacon Chain, and did not reduce the supply.
The Ethereum burns come from the contract’s complete record of Burn logs, and the seven quarterly burns were re-checked from their transaction receipts. The contract’s total supply just before the swap began is exactly 200,000,000 minus these 30 burns.
BNB Beacon Chain shut down on 19 November 2024 (block 384,544,850), so its burns come from its explorer, which BNB Chain keeps online. Each record was captured with a checksum. The explorer lists 23 BNB burn transactions in all: these 22 and the mirror burn. 200,000,000 minus all 23 equals Beacon Chain’s final BNB supply, 148,930,232.1730123, so none is missing.
Burns of ERC-20 BNB after the swap do not reduce BNB’s supply, and Beacon Chain has shut down, so both histories are closed. On the burn calendar they account for every day up to today.
Quarterly burns on BNB Smart Chain
The BNB in every native transfer from the quarterly-burn address (0x0038…18c9) to the dead address (0x…dEaD) on BNB Smart Chain, from burn #27 on 24 April 2024. Each must be a plain transfer with a successful receipt. Burns #27 to #37, the latest on 19 October 2026, total 17,704,059.6885 BNB.
The quarterly-burn address has sent nothing but these burns. Its transaction count (nonce) rose by one with each of them, and every update reads it, so a burn can’t be missed.
Any other transaction from that address stops this line and the gas-fee line until it is reviewed. So does more than 100,000 BNB reaching the dead address from anywhere else within one update (at most 1,000 blocks), so a quarterly burn from a new address is checked before it is counted.
The dead address has no code and no one is known to hold its key, so BNB sent there can never move.
Gas-fee burns and other sends
The line holds two things. Since block 13,082,000 (30 November 2021), BEP-95 sends part of the gas fees in every block to the dead address: 10% as of September 2026. And people and contracts send BNB there themselves. The largest case is 130,434.78 BNB on 10 to 12 September 2020, the days of Spartan Protocol’s SPARTA distribution, which gave its SPARTA token to anyone who sent BNB to the dead address through its contract.
A later update will show the BEP-95 burn on its own. Until then this line includes both.
Balances are read from an authenticated NodeReal archive node at an exact block, identified by its hash. The history from BNB Smart Chain’s first block on 29 August 2020 is the dead address’s balance at the last block of each UTC day. Every block that added 1,000 BNB or more, and every day that added 1,000 BNB or more outside such blocks, was reviewed before it was imported.
Each update reads the balance again and stops without moving on if it fell, or if the quarterly burns exceed its growth. The day amounts of this line and the quarterly burns always add up to the dead address’s balance.
Permanently locked (zero address)
The native BNB held by the zero address (0x0000…0000) on BNB Smart Chain, recorded as its growth per UTC day.
Almost all of it, 97,043.93 BNB, arrived on 31 May 2025. Venus Protocol’s governance proposal VIP-503 redeemed the BNB that the attacker in the October 2022 BNB Smart Chain bridge exploit had supplied to Venus, and sent 90% of it to the zero address. That BNB was created by the exploit and was never part of the original 200,000,000 BNB. It is counted because it can never move again. The rest is many small sends since 2020.
No one is known to hold a key for the zero address, so BNB sent there can never move. Its balance is read and checked like the dead address’s on every update. The VIP-503 transfer is in BNB Smart Chain block 50,653,632. Its transaction (0x51daa628…9dc3d1f) and receipt were read from a NodeReal archive node, and the proposal’s name comes from Venus’s governance records.
What the record covers
Coverage starts when BNB was created on Ethereum, at block 3,978,343 on 5 July 2017. The supply baseline is a fixed 200,000,000 BNB, the supply BNB was created with on Ethereum and issued with on Beacon Chain. The burned share is total burned ÷ 200,000,000.
On the burn calendar, a day without a BNB burn shows as 0 once every line has proven it: the BNB Smart Chain lines when an update has checked the balances past the end of that day, and the two closed histories for every day.
No date or size of the next quarterly burn is estimated.
How this total differs from Binance’s
Binance’s burn announcements since burn #13 also count Pioneer Burn Program credits: 146,252.71 BNB of lost coins, such as BNB sent to contracts by mistake, that Binance counted as burned although no transaction destroyed them. They are not counted here, so this total differs from Binance’s official figure.
BNB Chain’s own supply figure, 131,512,085 BNB after burn #37, is a reference only. Its figure after burn #36, 133,166,127.91 BNB, differed by about 0.73 million BNB from 200,000,000 minus the burns BNB Chain had announced, and BNB Chain does not explain the difference. Its post for burn #37 gives no total for the gas-fee burns, so the comparison can’t be repeated for the newer figure.
Why 200,000,000 minus this total is not BNB’s supply
Two amounts affect any comparison with the 200,000,000 baseline. The zero-address line includes 97,043.93 BNB created by the 2022 exploit, so the burned share counts BNB that was never part of the baseline. And the Ethereum line counts all 11,654,397.7575 BNB burned before the swap, but the mirror burn covered only the whole 11,654,397 BNB, so 0.7575 BNB burned on Ethereum was never taken off the supply that moved to Beacon Chain and BNB Smart Chain.
Because of these two amounts, 200,000,000 minus this total is not BNB’s current supply.
What is not counted
- Pioneer Burn Program credits, described above.
- The mirror burn on Beacon Chain and the swap burns on Ethereum, described above.
- The BNB held by BNB Smart Chain’s Token Hub for balances left on Beacon Chain, which their owners can still claim.
- BNB on opBNB, BNB Greenfield or other chains, and wrapped or pegged BNB.
- Addresses that only look like burn addresses.
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. On a tracker with a line read once per UTC day, which adds nothing to the current day until it closes (the HyperCore lines of HYPE and PURR), they add the last 7 or 30 closed days instead, and the card names the last one. A day with no record adds zero, and opening balances are left out. |
| Latest burn | The newest burn record, or the newest UTC day with a burn when that day is later (for lines kept as daily totals). A transfer into a burn address worth less than $1 at the latest price, and a day whose burns are worth less than $1, are passed over as dust; they still count in every total. Fee burns are never dust, however small. |
| 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. |
