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_7d / 7) / (burned_30d / 30)
usd_burned_24h  = burned_24h × current_price
annualized_pct  = burn_rate_hourly × 24 × 365 / circulating_supply × 100

burned_24hcomes from supply snapshots taken every 5 minutes (exact); until a token has 24 hours of snapshots it is estimated from today's and yesterday's daily totals and marked “est.”. Period USD values use the current price. The annualized figure extrapolates the 30-day pace.

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)
       // 7-day pace ×0.1 vs 30-day pace → 0, ×1 → 50, ×10 → 100
       // no 30-day data → 50 (neutral); zero burns in 30 days → 0

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 exceptional against the token's ownrecent history, so a “major” SHIB burn and a “major” BONK burn are both large for that token. The rules, in increasing order:

• Unusual — amount ≥ 1% of the total burned in the previous 30 days.
• Major — amount ≥ 5× the average daily burn of the previous 30 days.
• Exceptional — amount > 30-day average + 3 standard deviations, or ≥ the largest single day of the previous 365 days.

Windows exclude the event's own day; days without burns count as 0; tokens with less than 30 days of history are not classified. A rule that cannot trigger (e.g. zero burns in the last 30 days) is skipped. Hover any level badge in the events table to see the rule and the token's current threshold in tokens.

Net supply change

Burns alone do not prove an asset is deflationary: if a protocol mints 10M tokens and burns 2M, net supply grew by 8M. Since September 14, 2026 we snapshot on-chain total supply and circulating supply daily, which gives:

net_change     = circulating_today − circulating_yesterday   // negative = supply shrank
minted_amount  = net_change + burned_amount                  // 0 for fixed-supply tokens; > 0 = issuance
net_inflation_annualized = Σ net_change(N days) / circulating × 365 / N

Days before September 14, 2026 have no snapshot and are shown as “no data”. Net supply charts appear on token pages as history accumulates.

Tone of coverage

On article cards, story pages and topic pages we show how a publication frames an entity — favorable, neutral or critical. The label is produced per article by our news service, only for articles that name a person or organisation in the headline, and only when the model's confidence is at least 60%. Every label carries the quote that justifies it; hover the tone bar or open the evidence to see it.

• On a story, each source gets one vote per entity, regardless of how many articles it published. We show the block only when at least 3 sources are involved.
• On a topic page, the 30-day view counts articles, lists each publication's lean (−1 = all critical, +1 = all favorable, minimum 3 articles) and shows up to five favorable and five critical quotes with links.
• Tone measures how coverage is written, not whether the coverage is right, and it is not a judgement of the publication. We never call it “bias”.

Story summaries and breaking

Story pages open with an “In short” paragraph and a timeline. Both are written by our news service from the articles in the story (at least 3 sources), and refreshed when 3 new sources appear. They are the only text on those pages that is ours; headlines and images belong to the publishers and link to them. A story is marked breakingfor six hours when, within its first hour, it was covered by more distinct sources than a daily-recalculated threshold for its language — the word “BREAKING” in a headline does not count.

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.