Skip to main content
This feature is only available to Pro users.

Overview

The Burn Page provides an in-depth view of a project’s token burn activity. Burns directly impact token scarcity and supply dynamics, so this page captures every confirmed burn event and aggregates total value, supply offset, and underlying rationale — giving a clear picture of whether a project’s deflationary design is structural, sustained, or symbolic.
Image

Access

You can access the Burn Page by selecting any token from the Burn Screener or directly from its project profile. Each Burn Page includes a summary panel, a historical chart, and a burn event table.

Features

Using Burn

On the left you’ll see an overview summary of the burn information:
  • Total Burn (USD): Total value of tokens burned across all burn events, denominated in USD.
  • Total Burn (Token): Total number of tokens permanently removed from supply.
  • Supply Offset: The percentage of circulating (or released) supply offset by cumulative burns.
  • Burn Type: Classification of the burn mechanism type and methodology.
  • Burn Reasons: The primary rationale or purpose behind burn events.
The Burn Chart visualizes cumulative burns over time, overlaid with token price and burn value in USD. You can toggle between 7D, 1M, 1Y, or All Time views, and switch between absolute and percentage scaling for supply offset comparisons. Hovering over the chart displays precise values for each date and cumulative totals. Below the chart, you’ll find a detailed table of all the latest 10 burn events. Each row includes:
  • Date: Timestamp of the burn event.
  • Burn Value (USD): USD value of tokens burned.
  • Burn Amount (Token): Quantity of tokens removed.
  • Burn Type: Mechanism classification.
  • Burn Reason: Context for the burn.
  • Source / Transaction: Link to the originating on-chain transaction or record.

Burn Types

TypeDescription
ProgrammaticBurns that occur automatically according to protocol rules, such as fee burns, validator penalties, or on-chain logic. These are predictable and repeatable mechanisms embedded in the system’s design.
Non-ProgrammaticBurns executed manually or through discretionary decisions by the team, foundation, or community. Typically one-off or periodic, often based on governance votes, treasury decisions, or strategic adjustments.

Burn Reasons

ReasonDescription
GovernanceBurns decided through community or on-chain governance, such as proposals to reduce supply or allocate treasury funds to burn.
Protocol DesignBurns that are an inherent part of how the protocol operates. For example, automatic burning of transaction fees or gas fees.
Project DecisionBurns initiated by the project’s core team or foundation, often as part of treasury management, tokenomics realignment, or discretionary supply reduction.

Where to next