UNUS SED LEO Loading data

LEO burn tracker

Track irreversible LEO burns on Vaulta, independently matched across two chain indexers.

Total burned — LEO indexed burns

Checking sources Loading current status

Burned today — Loading latest UTC day

7-day burn — Loading seven-day average

30-day burn — Loading 30-day average

Total burned supply Loading supply reference

Burn history

Burn activity over time

Burned at — Loading transaction

Amount — Loading mechanism

Usual gap between burns — Loading recent burns

Move across the chart to inspect a date.

Mechanism	Share of burns	Burned	Status

Daily totals

Daily burn pace

Loading history

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

Daily burn pace —

Time to burn another 10% of supply —

Current 30d average

Selected pace

Straight-line estimate. It does not predict token price, network activity, or future policy.

Burn calendar

Daily burn calendar

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

Burned share of supply

— 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 LEO burn total is calculated

LEO exists on Ethereum and on Vaulta, the chain formerly called EOS, but every LEO burn so far has happened on EOS/Vaulta. The total counts each one as an irreversible burn on the LEO contract, verified on that chain.

Which LEO burns are counted

Canonical Vaulta contract burns

A LEO burn is a transfer action on the bitfinexleo1 contract whose destination is bitfinexleo1 itself and whose memo is burn. The tracker adds up the exact LEO quantity, to 4 decimals, of every such action that has become irreversible.

For each burn it verifies the transaction ID, the action’s sequence number, that the action executed, that it is behind the irreversible boundary, and its block, timestamp, contract, destination, memo and amount.

Historical burns were cross-checked between two Hyperion history providers, with evidence from Greymass. A new burn is accepted only when both providers agree.

What the record covers

Coverage begins on 14 June 2019.

No LEO has been burned on Ethereum. The Ethereum token’s supply is still the 660,000,000 LEO it was issued with, and every row in Bitfinex’s burn feed is an EOS/Vaulta transaction.

When checked on 27 September 2026, one billion LEO minus this total equalled Bitfinex’s reported supply exactly. Bitfinex’s burn feed adds up to 2,445,529 LEO less than the chain record, so totals built from that feed come out lower.

What is not counted

LEO that Bitfinex has bought back but not yet burned (its pending and accumulator balances). It is counted only once its burn transaction is on chain.

How the figures on this page are calculated

Every tracker works out its figures the same way. Days are UTC calendar days.

Figure	How it is calculated
Total burned	Every accepted daily amount of every mechanism, from the date that mechanism’s coverage starts. A record counts only once it is final: a finalized burn record, or a finalized daily figure from the chain’s official data provider. Duplicates and records held back for review stay out.
Today, 7-day and 30-day burn	Burns are added up by UTC calendar day. Today is the current UTC day. The 7-day and 30-day figures add the current day and the 6 or 29 days before it. A day with no record adds zero, and opening balances are left out.
Daily and moving averages	The 7-day and 30-day averages on the cards divide those totals by 7 and 30. The average lines on the charts are plain averages of the last 7, 30, 90 or 365 daily rows, or of as many as there are.
Daily USD estimate	The day’s burn × the last CoinGecko USD price stored on that same UTC day. It is shown with ≈ and rounded. It is left out when no price was stored that day, and on cumulative-chart points that include an opening balance, because that balance built up before the date shown. It is a reference value: not the price at the time of each burn, not a volume-weighted price, and not sale proceeds or an exact trade value. The figure for the current UTC day can still change as burns and prices arrive.
Burned supply	Total burned ÷ the all-time peak supply × 100. That baseline is not the latest circulating supply, and it comes from a different source than the market data.
Mechanism and contributor shares	A mechanism’s amount ÷ the total burn on record, or a known contributor’s amount ÷ that total. Burns with no known sender stay in the total and are not assigned to anyone.
Cumulative chart	For the range you select, the chart starts at the all-time total minus the days in the range, then adds each UTC day back in order. The change over the range is the last value minus the first.
Burn calendar	A cell is the sum of all mechanisms for that day. Its colour ranks the day against the others, by relative size or by percentile, and never changes the amount. A day with no record is blank, which means unknown. The exception is a tracker whose every mechanism proves the day, in one of two ways. Either the mechanism holds every transfer into its burn addresses, or their exact balances, from the start of its coverage, 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. On those trackers a day with no burn shows as 0.
Time to burn another 10%	(Latest reported total supply × 10%) ÷ the selected daily burn pace ÷ 365.25, in years. It is a straight-line scenario, not a forecast: it assumes supply policy, issuance, activity and burn rate all stay as they are.