PancakeSwap Loading data

CAKE burn tracker.

See how much CAKE's supply has shrunk since its peak, and every CAKE sent to the dead address, most of it minted the same week.

Net supply drop since the peak — CAKE since the peak

Loading the gross burns.

Checking sources Loading current status

Burned today (gross) — Loading latest UTC day

7-day burn (gross) — Loading seven-day average

30-day burn (gross) — Loading 30-day average

Net supply drop Loading supply reference

Net supply

CAKE net supply over time

Move across the chart to inspect a date.

Net supply is CAKE's total supply minus the CAKE at the dead address, the CAKE contract, 0x…0001 and 0x…0002. It is read at the block of each weekly burn (at the end of each day before 15 September 2021) and held until the next one.

Burn history

Burn activity over time (gross)

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 (gross)

Loading history

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

Burn calendar

Daily burn calendar (gross)

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

Net supply drop as a share of the peak

— 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 CAKE net supply drop and burn totals are calculated

Global verification standard →

CAKE's emission builds up at 44 CAKE per BNB Smart Chain block and is minted in weekly lumps, and most of it is burned within a week, so this tracker leads with how much CAKE's supply has shrunk rather than how much has been burned. Net supply = CAKE's total supply − the CAKE at the dead address − the CAKE held by the CAKE token contract, 0x…0001 and 0x…0002. It is read at the block of each weekly transfer from PancakeSwap's burn Safe to the dead address, and at the last block of each UTC day before the first such transfer on 15 September 2021; every day holds the latest reading. The net supply drop is the highest reading, 392,073,932.81 CAKE right after the burn of 11 September 2023, minus the latest reading, and its share is that drop ÷ 392,073,932.81. The homepage, category and dashboard rankings use the same net figures for CAKE: for any period, the change between the readings held at its start and its end, signed, so a period in which more CAKE was minted than burned is negative. The two lines below are gross: every CAKE ever sent to the dead address or locked for good.

Burned (dead address)

Calculation: Burned = the sum of the CAKE amounts in finalized Transfer logs from the CAKE contract (0x0E09FaBB…e81cE82) into 0x…dEaD since CAKE was created, whoever sent them. Since 15 September 2021 almost all of it has come from PancakeSwap's burn Safe (0xcEba6028…770a4a0e), a multisig wallet that needs 3 of its 7 owners to sign, which sends one transfer to the dead address about once a week. Most of each weekly burn is CAKE minted that week. CAKE's emission builds up at 44 CAKE per BNB Smart Chain block and is minted in weekly lumps by MasterChef v1, the only contract that can mint CAKE, and the part that farms do not use (99.7% as of September 2026) is sent to the burn Safe. Between the burns of 21 and 28 September 2026, 59,099,392 CAKE was minted and the burn Safe burned 59,427,617 CAKE, so the newly minted CAKE was about 99% of that burn and the net supply fell by 328,463.83 CAKE. Before 15 September 2021, 102 other addresses sent 221,429,168.36 CAKE to the dead address.
Evidence and coverage: 0x…dEaD is the standard burn address: no one is known to hold its key, and its CAKE balance has always equalled the CAKE sent to it, so none has ever left. The history from CAKE's creation at BNB Smart Chain block 693,963 (22 September 2020) is a fixed-cutoff set of logs, read from an authenticated NodeReal archive node, whose sum equals the address's on-chain balance at the cutoff (block 124,944,124, 30 September 2026). It holds all 265 transfers from the burn Safe that PancakeSwap lists, from 15 September 2021 to 28 September 2026. Each update reads new logs from the same provider, adds them to a running total and stops without moving on if that total differs from the dead address's balance or if CAKE's total supply has fallen.

Permanently locked

Calculation: Locked = the sum of the CAKE amounts in finalized Transfer logs from the CAKE contract into three addresses: the CAKE token contract itself (156,166.56 CAKE at the cutoff), 0x…0001 (2,080.63 CAKE) and 0x…0002 (43.64 CAKE).
Evidence and coverage: The CAKE contract has no function that can move its own balance. 0x…0001 and 0x…0002 are the addresses of built-in functions (precompiles), which have no code that can move tokens, and no one is known to hold a key for either. Each has always held exactly the CAKE sent to it, and each is checked against its on-chain balance on every update.

Coverage boundary and exclusions

Coverage starts when CAKE was created, at BNB Smart Chain block 693,963 on 22 September 2020. CAKE has no burn function and its total supply never falls: it is every CAKE ever minted. The peak is read right after a weekly burn because CAKE is minted in weekly lumps; a reading at any other time would include CAKE minted and waiting to be burned, and would swing by up to about 60 million CAKE within a week. A reading can still include some of that CAKE when PancakeSwap's weekly burnCake call has not run before the burn, or when CAKE is minted later in the burn's own block, and the next reading measures the level again. Each new reading stops the update for review if it moves more than 10,000,000 CAKE, if the burn Safe still holds more than 1,000,000 CAKE after the burn, or if PancakeSwap's weekly burnCake call last ran more than 36 hours before the burn. The update also stops if the dead address gains more than 1,000,000 CAKE on a day without a burn from the burn Safe, or if no burn arrives for 10 days. Every reading in the history was checked against these rules: one was flagged (18 April 2022, the day MasterChef v2 started) and kept after review, and none was dropped. PancakeSwap's own peak for that week, 391,560,247.39 CAKE, is lower: it counts the claim-contract transfer below as burned and does not subtract the 123,722.50 CAKE then at the locked addresses. PancakeSwap counts two transfers as burned that never reached a burn address, so its burn total is 5,931,409.03 CAKE higher than this tracker's Burned (dead address) line: 637,407.92 CAKE sent from the burn Safe to a claim contract on 10 May 2022 (transaction 0x38a99000…9d15), and 5,294,001.10 CAKE sent to PancakeSwap's team Safe on 21 April 2025 for the StakeDAO and CakePie lockers when veCAKE was retired (0x39e81c1d…e115). Both stay in the net supply here. PancakeSwap says an equal amount is still locked in its old CAKE Pool; that is not proven on chain, so nothing is added for it. PancakeSwap also publishes a weekly supply figure. Allowing for those two transfers and the locked addresses, it matches this tracker's reading to within 1 CAKE in 198 of the 264 weeks compared. Most larger differences are in the CAKE counted as minted: in 18 weeks PancakeSwap counts 1.06 to 13.31 million CAKE more than CAKE's total supply held at that week's burn, always a whole multiple of the 44 CAKE of emission per block, and the next week agrees again. PancakeSwap does not say when it takes each week's figure, so a reading taken some hours after the burn, which would explain this, is not verified. Not counted: CAKE in the burn Safe, which its signers can move; CAKE locked in the bridge contract for CAKE on other chains, and that bridged CAKE itself; and addresses that only look like burn addresses, such as 0xdEAD…42069. Since January 2026 PancakeSwap's governance has capped CAKE's supply as PancakeSwap counts it at 400,000,000 CAKE, but no contract enforces the cap. No date or size of the next burn is estimated. On the burn calendar, a day without a CAKE burn shows as 0 once an update has checked both lines' balances past the end of that 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.
Net supply drop since the peak: The peak reading minus the latest reading. Net supply = total supply − the CAKE at the dead address, the CAKE contract, 0x…0001 and 0x…0002, read at the block of each weekly burn; every UTC day holds the latest reading. The peak is the highest reading.
Share of the peak: Net supply drop ÷ the peak net supply × 100. In the rankings a period's figure is the reading held at the end of the day before the period minus the reading on its last day (for All, the peak minus the latest reading), ÷ the peak × 100; it is negative when more CAKE was minted than burned.
Minted and burned in the last week: Between the last two readings: burned = the rise of the CAKE held by the four addresses above; minted = the rise of CAKE's total supply; the net supply falls by burned minus minted.
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.