The LUNC burn tracker that reads the chain itself

How the live LUNC burn meter works

The meter at the top of this page does one simple thing, and does it in your browser. It asks public Terra Classic nodes for the total supply of LUNC, then subtracts that from the supply at block 7,790,000, the post-crash peak of 6,907,005,702,213 LUNC reached on 27 May 2022. The difference is shown as “removed from supply”, together with the share of the peak it represents, the block it read and what those coins would be worth at the live price.

Why is that a fair way to count burns? Because Terra Classic mints nothing new. The mint module’s inflation parameter is zero, and so is its annual provision, so the only way total supply can move is down. Every coin that disappears was destroyed by the burn module. That makes the meter a net figure: it counts tax burns, Binance batches, the big Terraform Labs wallet burn and every manual burn together, without needing to know which is which. By that measure, roughly 462 billion LUNC is gone, a little under 7% of the peak. Inflation is a governance-set parameter, so it could change by vote, and the meter would then need a second line for new coins.

The meter also shows the live burn tax rate. Keep in mind that this is the gross rate set by governance, 1.5% since proposal 12223 passed on 2 August 2026. Only 80% of that is burned, so 1.2% of a taxed transfer actually leaves supply. Our burn tax guide covers the rate history, the split and which transfers pay it.

If you compare our figure with another LUNC burn tracker, you may see a gap of a few hundred million coins. LuncScan, for example, uses a community baseline of 6,907,376,873,714 LUNC labelled 13 May 2022, about 371 million higher than the block 7,790,000 reading we use. Both methods are honest. They just start the clock at slightly different points, so neither is “wrong” by that margin.

Where burned LUNC comes from

Not all burns are alike. Four kinds of activity feed the burn module, and they differ hugely in size and in how predictable they are.

The on-chain burn tax. Normal sends, multi-sends, swaps, messages run through authz and coins that contracts pay out to wallets are taxed. With the 1.5% rate and the 80/20 split, 1.2% of each such transfer is burned in the same block, 0.15% goes to the community pool and 0.15% to the oracle reward pool that pays stakers. Trading inside an exchange, staking actions and IBC transfers are not taxed, which is why tax burns depend on how much LUNC actually moves on-chain.

Binance fee burns. Binance burns 50% of the trading fees it earns on LUNC spot and margin pairs, sent in monthly batches from its hot wallet to the burn address. Its own last published cumulative was about 82 billion LUNC, and adding the on-chain batches that followed gives a supportable total of more than 87 billion. Batch sizes, dates and the odd October repeat are on our Binance LUNC burn page.

The one-off Terraform Labs wallet burn. The single largest source by far. LuncMetrics attributes about 249 billion LUNC, roughly 54% of everything burned, to one TFL wallet. We could not verify the date of that burn independently, and the wallet holds only a tiny balance now. A later signal proposal to burn the remaining TFL wallets, 12202, was rejected in November 2025, so no repeat is scheduled. The Terra Luna crash page explains how TFL ended up holding those coins.

Community and manual burns. Anyone can send LUNC to the burn address. Projects such as DFLUNC, LunaticsToken and TerraCasino appear in the top burner lists, and Bitkub shows up mostly through tax paid on its own transfers. Individually these are small next to the three big sources, but together they make up a few percent.

Those shares come from LuncMetrics, a third-party dashboard, and we have not confirmed them on-chain. Its categories also overlap slightly: its Binance figure, for example, includes tax paid on Binance’s own transfers and user withdrawals sent to the burn address. Read the chart as “about half TFL, a quarter tax, a fifth Binance”, not to the decimal. The takeaway matters more than the precision: the steady, everyday burn from the tax is only about a quarter of the total, and the biggest single slice will not happen again.

The burn address, and why its balance is always zero

The LUNC burn address is terra1sk06e3dyexuq4shw77y3dsv480xv42mq73anxu. It is not a normal wallet. It is the account of the chain’s burn module, and the treasury module destroys whatever it holds at the end of every single block. Query its balance at any moment and you get nothing back. That is the system working, not a bug.

This matters because older guides and some dashboards still show a “burn wallet balance” that grows over time. That describes how things worked before 2022, or it is simply wrong. You cannot read total burned from the address. You read it from the drop in total supply, which is exactly what the meter does.

A manual burn is just a normal send to that address, so it pays the burn tax like any other transfer. Here is a labelled example. If you send 1,000,000 LUNC and your wallet adds enough fee to cover the tax, the burn module receives the full 1,000,000 and the 15,000 LUNC tax is charged on top: 12,000 of it is burned too and 3,000 goes to the two pools, so 1,012,000 LUNC leaves supply. If the fee does not cover the tax, the chain uses its “reverse charge” and takes the tax out of the amount sent: 985,000 reaches the burn module, 12,000 of the tax is burned as well, and 997,000 LUNC is destroyed in total.

How to verify LUNC burns yourself

You don’t have to trust our meter or anyone else’s. Every number on this page can be checked against public nodes in a couple of minutes, with nothing more than a browser.

1. Read total supply

   Open the /cosmos/bank/v1beta1/supply/by_denom?denom=uluna endpoint on a public Terra Classic node. The amount is in uluna, so divide by 1,000,000 to get LUNC.

2. Subtract it from the peak

   Take 6,907,005,702,213 LUNC, the total at block 7,790,000, and subtract the figure you just read. That is the net amount removed since the peak.

3. Confirm nothing is minted

   Check /cosmos/mint/v1beta1/inflation. A result of zero means every drop in supply is a burn, not a transfer between wallets.

4. Watch a burn happen

   Look up the burn address in a block explorer. A burn shows up in the block events as a burn event with the burner set to the burn module and the mode set to EndBlock.

5. Check the live tax

   Read /terra/tax/v1beta1/burn_tax_rate for the gross rate and burn_tax_split in the treasury params for the share that is not burned.

For the explorer step, Galaxy Finder shows full event logs, and our own LUNC explorer decodes a transaction hash or wallet in plain language. Repeat step one an hour later and you will see supply has fallen. A single reading we took dropped by about 2.7 million LUNC in 37 minutes, which is a nice way to see the burn without any dashboard at all.

Ready to hold the coins you’ve been tracking?

No local exchange pair? Start with USDT by card, send it to an exchange that lists LUNC, buy there and withdraw to your own wallet.

Create account

How fast is LUNC burning?

The honest answer is: slower than the headline totals suggest. LuncScan’s all-time average works out to around 280 million LUNC per day, but that average is inflated by the one-off TFL burn. Strip that out and look at 2026 alone, and the picture is calmer. Trackers showed roughly 444 billion burned in April and May 2026 and about 463 billion by early November, so around 19 billion in six months. LuncMetrics recorded close to 600 million in one autumn seven-day window. Both point to something like 80 to 110 million LUNC a day, or 30 to 40 billion a year, with a jump on the day Binance sends its batch.

The tax change in August 2026 is the wild card. Moving from 0.5% to 1.5% tripled the burned share of each taxed transfer, from 0.4% to 1.2%. Whether total tax burns triple depends on behaviour: some users and bots move less LUNC on-chain when it costs more. We would rather watch a few months of supply data than guess, and the meter makes that easy. For context on the vote and its tally, see our governance guide; for headlines as they land, see LUNC news.

One more thing about the burn rate: it is measured in coins, not dollars. If the price rose, Binance’s 50% fee share would buy fewer coins to burn, and the tax would burn the same percentage of whatever moves. A rising price tends to slow the burn in coin terms, which is the opposite of what many “burn countdown” posts assume.

Why “burn LUNC to $1” math doesn’t work

With roughly 6.44 trillion LUNC in existence, a price of $1 means a market cap of about $6.4 trillion, thousands of times the low hundreds of millions of dollars LUNC is valued at. Burning cannot close that gap on any reasonable timeline. At the generous 280 million a day all-time average, removing just 1 trillion LUNC would take about ten years; at the recent pace it would take closer to 25 to 30. And even after a trillion is gone, more than 5 trillion would remain.

This is arithmetic, not a forecast, and it cuts both ways: burns do reduce supply steadily, they just do it in single-digit percentages over years. Our can LUNC reach $1 page runs the same math for $0.001, $0.01 and other targets, and the LUNC supply page explains why the circulating figure on price sites is lower than the on-chain total.

Burned means gone

A burned coin is destroyed in the same block it reaches the burn module. It does not sit in a wallet waiting to be spent, and no one holds a key to bring it back.

Other LUNC burn trackers worth knowing

Several community sites track LUNC burns. They read the same chain, so their totals should agree within the baseline difference explained above. If one is far off, it is usually stale or reading an old endpoint.

Explorers are the other half of the toolkit. Galaxy Finder, Terraport Finder, LUNCdash Finder and ATOMScan all show burn transactions and events. Mintscan does not support Terra Classic, even though a page for it loads.

Why some LUNC dashboards show a 0% burn tax

If a wallet, bot or dashboard tells you the LUNC burn tax is 0%, it is almost certainly reading the wrong place. Until December 2024 the tax lived in the treasury module. The v3.3.0 upgrade, proposal 12148 at block 21,163,600, moved it into a new x/tax module and set the old treasury rate to zero. The old /terra/treasury/v1beta1/tax_rate endpoint still answers, and it still says 0. The live rate is at /terra/tax/v1beta1/burn_tax_rate. You can read more about that release on our network upgrades page.

Two related traps catch people too. First, the treasury parameter burn_tax_split reads 0.2, and it is easy to assume that means 20% is burned. It is the reverse: 0.2 is the share that is not burned, so 80% is. Second, some sites still say “1.2% burn tax” or “0.5%”. The rate is 1.5% since August 2026, of which 1.2 points are burned. Both the rate and the split are governance parameters, so they can change again by vote.

Check the chain

When you want to act on what you see, our how to buy LUNC guide walks through the route step by step, and LUNC staking explains how part of the tax ends up paying stakers through the oracle pool.