BNB Loading data

BNB burn tracker.

See BNB's quarterly burns since 2017 on Ethereum, BNB Beacon Chain and BNB Smart Chain, its gas-fee burn, and BNB sent to addresses no one can spend from.

Total burned — BNB indexed burns

Checking sources Loading current status

Burned today — Loading latest UTC day

7-day burn — Loading seven-day average

30-day burn — Loading 30-day average

Total burned supply Loading supply reference

Burn history

Burn activity over time

Burned at — Loading transaction

Amount — Loading mechanism

Usual gap between burns — Loading recent burns

Move across the chart to inspect a date.

Primary indexed: ——
Other indexed: ——

Daily totals

Daily burn pace

Loading history

7-day 30-day 90-day 365-day

Daily burn pace —

Time to burn another 10% of supply —

Current 30d average

Selected pace

Straight-line estimate. It does not predict token price, network activity, or future policy.

Burn calendar

Daily burn calendar

Loading 52-week UTC window

Active days — Loading elapsed UTC days

Longest streak — Consecutive days with indexed burns

Peak day — Loading indexed daily totals

Loading daily burn totals…

No daily record

Less More

Select a day to see its recorded burn total. A blank cell means there is no daily record; it does not mean zero tokens were burned.

Market context

Price history and reference levels

Checking market history

Move across the chart to inspect an exact price.

24-hour low: —
24-hour high: —
All-time high: —
All-time low: —
Below ATH: —
Supply ratio: —

Loading connected market data and reference levels.

Supply

Burned share of supply

— burned — current supply — initial supply

Rank	Entity	Direct	Fees	Total	Share	Txs

Largest indexed burn records ranked by token amount
Rank	Date / mechanism	Amount	Current value	Source events	Source
Loading largest indexed records...

Current value uses the latest available market price, not the token price when the burn occurred.

Loading burn index Loading records

Time	Type	Amount	Block	Source / Reference
Loading burn records...

Methodology

How the BNB burn total is calculated

Global verification standard →

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. Total burned = the burns on Ethereum (2017 to 2019) + the burns on BNB Beacon Chain (2019 to 2024) + the native BNB held by the dead address on BNB Smart Chain (the quarterly burns, and the gas-fee burns and other sends) + the native BNB held by the zero address on BNB Smart Chain (Permanently locked). BNB moved off Ethereum in 2019 and BNB Beacon Chain has shut down, so these two records are fixed. On every update, the BNB Smart Chain lines are checked against the two addresses' on-chain balances.

Burns before BNB Smart Chain

Calculation: Burns on Ethereum, 2017-2019 = the BNB in 30 successful burn() calls on the ERC-20 BNB contract (0xB8c77482…631bDD52), from 18 October 2017 to 16 April 2019: the seven quarterly burns (#1 to #7) and 23 smaller burns by Binance addresses and other holders, 38.76 BNB in total. Burns on BNB Beacon Chain, 2019-2024 = the BNB in 22 successful burn transactions from 28 April 2019 to 17 January 2024: the 19 quarterly burns (#8 to #26) and three test burns of 1, 1 and 0.1 BNB. Not counted: 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. Also not counted: the burns on Ethereum from 23 April 2019 on, which retired ERC-20 BNB as it was swapped for BNB on Beacon Chain rather than reducing the supply.
Evidence and coverage: 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, and 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, and on the burn calendar they account for every day up to today.

Quarterly burns on BNB Smart Chain

Calculation: Quarterly burns = 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 #36 total 16,057,863.2475 BNB.
Evidence and coverage: 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 cannot be missed. Any other transaction from it stops this line and the gas-fee line until it is reviewed, and 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

Calculation: For each UTC day, gas-fee burns and other sends = the growth of the dead address's native BNB balance − that day's quarterly burns. 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.
Evidence and coverage: 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, and 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)

Calculation: Permanently locked = 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, when 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.
Evidence and coverage: 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.

Coverage boundary and exclusions

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. 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. Also not counted: 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; and the mirror burn and swap burns described above. 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. BNB Chain's own supply figure, 133,166,127.91 BNB after burn #36, is a reference only: it differs by about 0.73 million BNB from 200,000,000 minus the burns BNB Chain announces, and BNB Chain does not explain the difference. No date or size of the next quarterly burn is estimated. 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.

Shared formulas

How the page derives every displayed metric

Total burned: Sum all accepted daily mechanism amounts on or after each mechanism's coverage boundary. Only finalized, published normalized events or accepted finalized provider-day observations enter the aggregate; duplicate identities and quarantined records do not.
Today, 7-day, and 30-day burn: Sum mechanism amounts by UTC calendar day. Today uses the current UTC day; the other cards sum the current day plus the preceding 6 or 29 UTC days. Missing days contribute zero. Reconciled opening balances are excluded from these pace windows.
Daily and moving averages: The 7-day and 30-day card averages divide those fixed UTC-window totals by 7 and 30. Chart lines are trailing arithmetic means over up to 7, 30, 90, or 365 available daily rows.
Daily USD estimate: Positive UTC-day burn amount × the last positive CoinGecko USD reference price stored within that same UTC day. It is displayed with ≈, rounded for readability, and omitted when no same-day price exists. Cumulative-history points containing a reconciled opening balance also omit it because that balance accrued before the displayed date. This is a reference valuation, not transaction-time pricing, VWAP, sale proceeds, or an exact execution value; the current UTC day can change as new burn and price observations arrive.
Burned supply: Total burned ÷ the disclosed all-time peak protocol-supply baseline × 100. The baseline is not the latest circulating supply and is sourced separately from market data.
Mechanism and contributor shares: Mechanism amount ÷ total indexed burn, or attributed contributor amount ÷ total indexed burn. Unattributed burns remain in the total and therefore are not reassigned to known entities.
Cumulative history and calendar: For a selected range, start at lifetime total minus the included daily rows, then add each UTC day back in order; the range change is the last cumulative value minus the first. Calendar cells sum all mechanisms per day and rank positive days by relative or percentile intensity, which changes color only—not the amount. A day with no row is blank (unknown), except on trackers whose every mechanism proves the day: either it holds every transfer into its burn addresses, or their exact balances, from its coverage start, 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. There, a day with no burn shows as 0.
Time to burn another 10%: (Latest reported total supply × 10%) ÷ selected daily burn pace ÷ 365.25. This is a straight-line scenario, not a forecast; it assumes no change in supply policy, issuance, activity, or burn rate.