basiliskawakens.xyz

What Does "Burned Tokens" Mean and How to See the Burn Address

Burned tokens are cryptocurrency tokens that have been permanently removed from circulation by sending them to an address from which they can never be spent or recovered. The burn address is that destination - a wallet with no known private key, typically all zeros or a well-known null address. You can see the burn address by looking up the token's transaction history on a block explorer like Etherscan or BscScan, filtering for transfers to the address 0x0000000000000000000000000000000000000000 or 0x000000000000000000000000000000000000dEaD.

Why tokens are burned

Burning reduces the total supply of a token. Projects do this for several reasons:

Burning does not increase the value of remaining tokens by itself - it only affects the supply side. Price depends on demand, market conditions, and many other factors.

How burns are recorded on-chain

A token burn is simply a transfer transaction where the recipient is a burn address. The data/token-name-symbol-scam-check/">token contract treats it like any other transfer: it decreases the balance of the sender and increases the balance of the burn address. Because the burn address has no private key, those tokens are locked forever.

Smart contracts can also call a burn() function directly, which destroys tokens from the contract's own balance or from a user's balance without sending them to an external address. In that case, the tokens are removed from the total supply but no visible "to" address appears in a standard transfer log. You would need to look at the contract's internal event logs (e.g., a Burn event) to see the amount and the address that initiated the burn.

How to Find the Burn Address on a Block Explorer

The two most common burn addresses are:

Some projects use other addresses they claim are unspendable. To check, you would need to verify that no transaction has ever sent ETH or tokens out of that address.

Steps to see a token's burn address and burned amount

  1. Go to the token's page on a block explorer. For an ERC-20 token on Ethereum, use Etherscan. For BEP-20 on BNB Chain, use BscScan. Enter the token's contract address in the search bar.

  2. Find the "Holders" or "Token Holders" tab. This lists all addresses that hold the token, sorted by balance. The burn address is usually the top holder if significant burning has occurred.

  3. Look for an address starting with 0x0000... or labeled "Burn Address." Etherscan and BscScan often label the zero address as "Burn Address" automatically. Click the address to see its full transaction history.

  4. Check the "Total Supply" vs. "Circulating Supply." On the token's main page, the explorer shows total supply (including burned tokens) and sometimes a separate "Circulating Supply" figure. The difference between them is the amount burned.

  5. For real-time burn data, use a burn tracker. Sites like burn.bot or token-specific dashboards on Dune Analytics track cumulative burns for popular tokens. These are not always accurate for obscure tokens, so verify on the explorer.

How to Verify a Burn Is Real

Not every transfer to the zero address is a bona fide burn. Some projects send tokens to a burn address but then use a proxy contract that can mint new tokens from that address - if the contract has a mint() function controlled by an owner, the burn is reversible. To confirm a burn is permanent:

Common Misconceptions

If you want to track burns over time, set up a custom alert on a block explorer for transfers to the zero address, or build a simple query on Dune Analytics using the token_transfers table filtered by the burn address.

Not financial advice. basiliskawakens.xyz publishes market data and general information about digital assets. Crypto assets are volatile and you can lose everything you put in. Nothing here is a recommendation to buy, sell or hold, and we make no price predictions.

Prices are sourced from third parties and may be delayed or wrong. Verify anything you intend to act on against a primary source.

Back to on-chain data