How the ASTER burn total is calculated
ASTER has no burn function, so an ASTER burn is a transfer to an address from which no one can ever spend it. The total adds up the ASTER in every finalized transfer on BNB Smart Chain, since the token was created, into two reviewed addresses.
The dead address is shown as Burned, and the ASTER token contract itself as Permanently locked. On every update, the running total for each address is checked against that address’s on-chain ASTER balance.
Which ASTER burns are counted
Burned (dead address)
Burned is the sum of the ASTER in finalized Transfer logs of the canonical ASTER contract (0x000Ae314…4f556A) into 0x…dEaD, whoever sent them.
From December 2025 to May 2026 the large burns were of ASTER the project had bought back: 77,860,328 ASTER on 5 December 2025 and 98,400,345.47 ASTER in three transactions on 5 February 2026. Both are marked on the cumulative chart. Three smaller burns in that period were airdrop tokens forfeited on early claims, 1,520,328.10 ASTER in total.
Since 29 June 2026 the burns, about every two weeks, come from the team’s reserve. The reserve is held in the team’s multisig wallet (0x59d8…3b19) and is not counted as circulating. Aster says each of these burns equals the ASTER it bought back with trading fees over the same period; the bought-back ASTER goes to stakers instead of being burned.
These burns cut ASTER’s effective total supply (8 billion minus everything burned) but not its circulating supply, because the reserve was not in circulation.
The contract itself still reports a total supply of 8 billion, because burned ASTER sits at the dead address rather than being destroyed.
0x…dEaD is the standard burn address. No one is known to hold its key, and its ASTER balance has always equalled the ASTER sent to it, so none has ever left.
The history from creation block 59,613,717 is a fixed set of BNB Smart Chain logs up to a cutoff, read from an authenticated NodeReal archive node, and their sum equals the address’s on-chain balance at that cutoff. Each update reads new logs from the same provider, adds them to a running total, and stops without moving on if that total differs from the dead address’s balance.
The team’s multisig wallet is not counted. It holds the rest of the team’s reserve and its signers can move it, so its ASTER counts only once it reaches the dead address.
Permanently locked
Locked is the sum of the ASTER in finalized Transfer logs of the canonical ASTER contract into the ASTER token contract itself.
The ASTER contract has no owner and no function to mint, burn, upgrade or withdraw tokens, so nothing can move the ASTER it holds, and a contract can’t sign the permit that would let it approve a transfer. Like the dead address, it has always held exactly the ASTER sent to it, so none has ever left, and it is checked against its balance on every update.
What the record covers
Coverage starts when ASTER was created, at BNB Smart Chain block 59,613,717 on 1 September 2025. The supply baseline is the fixed 8,000,000,000 ASTER created then. The contract can’t mint more, and every update checks that no ASTER has been created and stops if any has.
What is not counted
- Zero-value transfers, which move nothing.
- ASTER held at any other address, including the team’s multisig wallet and look-alike burn addresses such as 0x1111…1111, which can’t be proven unspendable.
- ASTER bridged to other chains, including Aster Chain.
- Burns of APX, the earlier token swapped 1:1 into ASTER in September 2025.
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. |