How the numbers are computed

Supply and total burned

• Initial supply — the token's supply at genesis (or at the point we started tracking it, when genesis data is unavailable).
• Total burned — cumulative tokens sent to recognised burn addresses (e.g. 0x…dead, the zero address) or destroyed via a burn function, on the monitored chain.
• Circulating supply — initial supply minus total burned, on the monitored chain.
• % supply burned — total burned ÷ initial supply.

Each token is monitored on one chain (shown on its page). For multichain tokens such as FLOKI or BABYDOGE we do not currently aggregate supply or burns from other chains — the figures cover the monitored chain only.

Burn rate

Burn rate is tokens burned per hour, computed in one of two ways depending on the chain:

• From burn events (Ethereum, Solana): we index every transfer to a burn address and sum them per hour. Each transaction appears in the “Recent Burn Events” table.
• From supply snapshots (BNB Chain, Base): we record the token's supply and burn-address balances at regular intervals and derive the rate from the change between snapshots. These tokens show a burn rate but no per-transaction events — that is expected, not a data gap.

Burn Impact

All Burn Impact metrics are relative to circulating supply, so tokens with wildly different supplies can be compared.

burned_24h_pct  = burned_24h / circulating_supply × 100
burned_7d_pct   = burned_7d  / circulating_supply × 100
acceleration    = burned_24h / average_daily_burn_30d
usd_burned_24h  = burned_24h × current_price
annualized_pct  = burn_rate_hourly × 24 × 365 / circulating_supply × 100

burned_24h is the burn recorded since 00:00 UTC; when it is unavailable we fall back to burn_rate_hourly × 24. The 30-day average excludes the current (partial) day. USD values use the current price, not the price at the moment of each burn.

BurnMonitor Deflation Score (0–100)

A single number that answers “how hard is this token being burned right now, relative to its size?”. Three components, each scaled 0–100:

S24  = logscale(burned_24h in ppm of supply,  lo = 0.001 ppm, hi = 100 ppm)
S7   = logscale(burned_7d  in ppm of supply,  lo = 0.007 ppm, hi = 700 ppm)
SACC = clamp(50 + 50 × log10(acceleration), 0, 100)
       // ×0.1 vs 30d avg → 0, ×1 → 50, ×10 → 100; no 30-day history → 50 (neutral)

logscale(x, lo, hi) = clamp((log10(x) − log10(lo)) / (log10(hi) − log10(lo)) × 100, 0, 100)

Deflation Score = round(0.40 × S24 + 0.30 × S7 + 0.30 × SACC)

• 1 ppm (part per million) per day = 0.0001% of supply per day ≈ 0.0365% per year.
• The log scale means each ×10 in burn intensity adds the same number of points. 100 ppm/day (≈3.65%/yr) saturates the score — very few tokens get close.
• The score measures burn intensity, not investment quality. A token can score high while its supply is still inflating via minting (see below).

Burn event levels

Each burn transaction is labelled normal, unusual, major or exceptionalby comparing its size with the token's own distribution of burn sizes over the previous 30 days. Thresholds are per token, so a “major” SHIB burn and a “major” BONK burn are both large for that token. The exact thresholds are set by our indexing backend and will be published here once they are frozen.

Net supply change (planned)

Burns alone do not prove an asset is deflationary: if a protocol mints 10M tokens and burns 2M, net supply grew by 8M. We are working on Burned − Minted = Net Supply Change and an annualized net inflation/deflation rate for the tokens where issuance can be measured on-chain. Until then, the metrics above describe burns only.

Burn & Tokenomics news

The news feed is filtered from a crypto news aggregator using fixed keyword queries (burn, buyback, token unlock, minting, circulating supply, deflationary). The category badge reflects the query that matched, so it is approximate. Headlines link to the original publisher; we do not republish article bodies.

Questions or corrections: contact us.