Dashboard · VantagePlanned

PancakeSwap Volume and CAKE Burn by Chain and Version

How much trades on PancakeSwap and on which chains, and how much CAKE does its revenue burn each week?

PancakeSwap's daily swap volume on v2, v3 and Infinity pools by chain, and the weekly CAKE buy-and-burn that its revenue pays for.

ShareEmail itvoltfincrypto.com/apps/pancakeswap-volume-cake-burn
Blueprint

What the dashboard will show.

The dashboard as it will open in Vantage. Each figure is named here and arrives with its receipt; until its data is published, its place stays empty.

  • Chain
  • Period

Volume

PancakeSwap's swaps and liquidity by version and chain.

Volume, latest day

USD

Swap volume across every covered PancakeSwap pool and chain on the latest complete day.

Figuredex_swaps_dailyAwaiting data

TVL

USD

Tokens held in PancakeSwap pools at the last block of the latest day, valued at oracle prices.

Figuredex_liquidity_dailyAwaiting data

BNB Chain share

%

BNB Chain's share of PancakeSwap volume over the selected period.

Figuredex_swaps_dailyAwaiting data

Infinity share

%

Volume in Infinity pools as a share of all PancakeSwap volume over the selected period.

Figuredex_swaps_dailyAwaiting data

Volume by version

USD

Daily volume over the period, stacked by v2, v3 and the two Infinity pool types.

Stacked barsdex_swaps_dailyAwaiting data

Chains

Each covered chain with PancakeSwap's volume, fees, liquidity and the split of its volume by version.

Tabledex_swaps_dailyAwaiting data

CAKE burn

Each week's burn, the revenue behind it and CAKE's supply after it.

CAKE burned, last week

CAKE

CAKE sent to the burn address in the last complete burn week.

Figuretoken_supply_dailyAwaiting data

Net supply change, last week

CAKE

CAKE emitted minus CAKE burned in the last complete week; a negative figure means supply fell.

Figuretoken_supply_dailyAwaiting data

What funded the burn

USD

The revenue behind the last burn by source, such as DEX fees and PancakeSwap's other products.

Donutprotocol_revenue_dailyAwaiting data

Burned and emitted by week

CAKE

CAKE burned and CAKE emitted in each week, with total supply after each burn.

Bar charttoken_supply_dailyAwaiting data

Chain
Every covered chain, or all
Period
Last 7, 30 or 90 days
About

What it answers, and for whom.

PancakeSwap started on BNB Chain in 2020 and now also runs on Ethereum, Base, Arbitrum and other chains. It has three generations of pools: v2 constant-product pairs, v3 concentrated-liquidity pools with fee tiers and Infinity, its v4 design, where pools share one vault, come as concentrated-liquidity or liquidity-book pools and can attach hooks. The volume page reads every generation's swaps and pool balances on each chain PancakeSwap runs on, so BNB Chain's share and Infinity's share can be followed day by day.

CAKE Tokenomics 3.0 retired veCAKE and its gauge votes in April 2025 and sent the trading-fee share that veCAKE holders used to receive to the CAKE burn. Each week PancakeSwap buys CAKE with protocol revenue and burns it, set against the CAKE still emitted as liquidity incentives. The burn page follows that loop: the revenue behind each burn, the CAKE burned and emitted each week and CAKE's supply after each burn.

Method

How it will be measured.

Every figure will be read at a block, kept with its source and its exact read, and open a receipt anyone can re-check.

How receipts work →
  1. v2 and v3 volume comes from each pool's Swap events, and Infinity volume from the Swap events of its concentrated-liquidity and liquidity-book pool managers, valued at the stablecoin leg or an oracle price at the swap's block.
  2. Liquidity is each pool's tokens at the day's last block; Infinity pools, which share one vault, are attributed their tokens from their own liquidity state.
  3. Weekly burns are the CAKE sent to the burn address in PancakeSwap's burn transactions, and emissions are the CAKE released to farms and pools over the same week, so the net change in supply is measured, not assumed.
  4. The revenue behind each burn is traced from the fee collection and swap-to-CAKE transactions before it, by source: DEX fees and PancakeSwap's other products.

The data it needs

Read from chain state and history

  • dex_swaps_dailyTo buildDEX volumeSwap counts and volume per DEX, pool and chain per day, decoded from Swap events, valued with stablecoin legs and oracle prices.
  • dex_liquidity_dailyTo buildDEX liquidityLiquidity held by each DEX pool at day end, in tokens and valued in USD, with fee tier and pool age.
  • token_supply_dailyTo buildToken supply by dayTotal supply of each registry token on each chain at day end: wrapped BTC, liquid staking tokens, tokenized assets and other tracked tokens.
  • protocol_revenue_dailyTo buildProtocol fees, revenue and buybacksFees users paid to each protocol and the part kept by the protocol or its token holders, per protocol and day, including buybacks.
  • native_prices_dailyTo buildOracle prices by dayReference prices of major assets read from on-chain oracle feeds (Chainlink latestRoundData) at each day's last block, with each round's update time.
  • PancakeSwap v2 and v3 factory events and each pool's Swap events on every covered chain
  • Infinity vault and pool manager Initialize and Swap events
  • Pool reserves and liquidity state at day-end blocks
  • CAKE transfers to the burn address and CAKE totalSupply at each burn block
  • CAKE emission contract releases to farms and pools
  • Fee collection and swap-to-CAKE transactions before each weekly burn
Questions

Questions people ask.

How is PancakeSwap volume measured?

Swaps are read from each v2 and v3 pool's Swap events and from the Infinity pool managers' events, since Infinity pools share one vault instead of holding their own tokens. Each swap is valued once, at its stablecoin leg or an oracle price at that block, and the chain table counts trades by transaction beside the volume.

What is PancakeSwap Infinity?

PancakeSwap's v4 architecture. All pools share one vault, which makes multi-hop trades and new pools cheaper. Pools come in two types, concentrated liquidity and a liquidity book of price bins, and either type can attach a hook that adds custom logic such as dynamic fees.

How does the CAKE burn work?

A share of PancakeSwap's revenue is used to buy CAKE on the market, and the CAKE bought is sent to a burn address each week, where it can never move again. The dashboard reads each burn transaction and the purchases that fed it.

What happened to veCAKE?

It was retired under CAKE Tokenomics 3.0. Gauge voting ended in April 2025, the fee share paid to veCAKE holders went to the burn instead, and locked CAKE could be redeemed one for one. Governance votes now count CAKE directly.

Is CAKE deflationary?

In a given week it is if more CAKE is burned than emitted. The net supply change tile shows that difference week by week, from the burn transactions and the emission contracts, rather than taking it from an announcement.

Which chains does PancakeSwap run on?

BNB Chain, where it started, plus Ethereum, Base, Arbitrum, ZKsync, Linea and others, and its interface also swaps across chains, including to Solana. The chain table shows volume and liquidity on each chain the dashboard covers.

Infinity
PancakeSwap's v4 design: one shared vault, two pool types (concentrated liquidity and liquidity book) and hooks.
Liquidity book
A pool type that holds liquidity in discrete price bins, each trading at a fixed price, instead of along a continuous curve.
Buy-and-burn
Using revenue to buy a token on the market and send it to an address no one controls, removing it from supply.
veCAKE
Vote-escrowed CAKE, retired in 2025, which gave locked CAKE voting power over emissions and a share of fees.

Build PancakeSwap Volume and CAKE Burn by Chain and Version on verified data.

Start free in Voltfin Studio: boards, tables and reports where every number opens its receipt. Tell us which data you need first and we will build it next.