SHIB burned, latest day
SHIBSHIB transferred into registered burn addresses during the latest complete UTC day, from Transfer events.
Dashboard · VantagePlanned
Shiba Inu Burn Tracker: SHIB Burned by Day and Source
How much SHIB has been burned, and how much is burned each day?
SHIB sent to burn addresses each day, the burns that come from Shibarium fees and the total ever burned, read from the SHIB token contract.
ShareEmail it
Blueprint
What the dashboard will show.
The dashboard as it will open in Vantage. Each figure is named here and arrives with its receipt; until its data is published, its place stays empty.
Burns
SHIB burned in the latest day and month, by source.
SHIB burned, 30 days
SHIBSHIB sent to burn addresses over the last 30 complete days.
Burn transactions, latest day
countTransactions that sent SHIB to a burn address during the latest complete day.
Shibarium share, 30 days
%The part of the last 30 days' burns that came through the Shibarium fee burn, by the path that sent it.
SHIB burned by day and source
SHIBSHIB burned each day in the selected period, split into Shibarium fee burns, community burn events and other holder burns.
Supply
Total burned, circulating supply and the largest burns since launch.
Total SHIB burned
SHIBBalances of every burn address plus any fall in totalSupply(), at the latest day's last block.
Share of supply burned
%Total burned as a share of the supply minted when the SHIB contract was deployed.
Circulating supply
SHIBtotalSupply() minus the balances of burn addresses at the latest day's last block.
Burned this year
SHIBSHIB sent to burn addresses since the first block of the current calendar year.
Largest burns since launch
The largest single burn transactions since launch, led by the 2021 Vitalik Buterin burn, with amount, date, sender label and block.
- Period
- Last 7, 30 or 90 days
About
What it answers, and for whom.
Most Shiba Inu burns are transfers to addresses that no one controls, such as the well-known dead addresses, so burned SHIB stays visible in their balances. This dashboard reads every SHIB transfer into those addresses on Ethereum and adds them up by day, so the burn count is what the chain recorded rather than a tally gathered from social posts.
The total burned is dominated by one transaction: in 2021 Vitalik Buterin sent most of the SHIB its creators had given him to a dead address. Daily burns since then are far smaller and come from holders, community burn events and Shibarium, the SHIB layer 2, part of whose base fees end up as SHIB burned on Ethereum. The page splits burns by source, so one large burn does not read as a trend.
Use it to check a burn claim before repeating it or to see whether daily burns are rising or falling. Circulating supply is read as total supply minus what sits in burn addresses, and every figure links to the transfers and the block behind it.
Method
How it will be measured.
Every figure will be read at a block, kept with its source and its exact read, and open a receipt anyone can re-check.
How receipts work →- Burns are SHIB Transfer events into a registry of burn addresses, starting with the long-used dead addresses, read from the SHIB contract on Ethereum and summed per UTC day.
- Total burned is the balance of those addresses at each day's last block plus any fall in totalSupply(), so a burn is counted once whichever way it happened.
- A burn is attributed to Shibarium when it comes from the path that swaps bridged Shibarium fees for SHIB, and to holders or burn events otherwise; each attribution rule is published.
- Circulating supply is totalSupply() minus the balances of burn addresses at the same block. Team or locked wallets are labelled but never subtracted silently.
The data it needs
Read from chain state and history
- token_supply_dailyTo buildToken supply by dayTotal supply of each registry token on each chain at day end: wrapped BTC, liquid staking tokens, tokenized assets and other tracked tokens.
- token_transfers_dailyTo buildToken transfer volumeERC-20 and native transfer counts, volume and unique senders and receivers per token per chain per day.
- whale_transfersTo buildLarge transfersTransfers above a size threshold per token and chain, with sender and receiver labels (exchange, fund, bridge, unknown).
- address_labelsTo buildAddress labelsLabels for known addresses: exchanges, bridges, protocols, funds, treasuries, sanctioned addresses and known attackers.
- SHIB ERC-20 contract on Ethereum: Transfer events into registered burn addresses
- totalSupply() and balanceOf() of each burn address at each day's last block
- Transactions on the Shibarium burn path that swap bridged fees for SHIB and burn it
- Burn addresses and burn contracts recorded in the address registry with the source of each
Questions
Questions people ask.
How much SHIB has been burned?
The total is the SHIB held by burn addresses plus any reduction in the contract's total supply, read at the latest complete day. The page shows it with the block it was read at; most of it comes from the single 2021 burn by Vitalik Buterin.
Where do burned SHIB tokens go?
Usually to addresses whose private key no one knows, such as the long-used dead address that starts with 0xdead. Tokens sent there can never move again, so the balance of each burn address is a running record of what was burned.
What is the Shibarium burn?
Shibarium, the Shiba Inu layer 2, collects a base fee on each transaction. Part of it builds up in a burn contract, and once anyone starts a burn the fees are carried to Ethereum, swapped for SHIB and burned. Those burns appear here as their own source.
Does a burn change SHIB's total supply?
A transfer to a dead address leaves totalSupply() unchanged, because the tokens still exist in that address's balance. That is why circulating supply is shown as total supply minus burn-address balances, with both reads named.
Why do daily burn numbers jump around?
A few large burns, often from a community event or a single holder, can outweigh weeks of small ones. The chart splits each day by source and the largest burns are listed with their transactions, so a spike can be traced to the transfer that caused it.
- Dead address
- An address whose private key is unknown, used as a destination for burns. Tokens sent there cannot be moved again.
- Circulating supply
- Total supply minus the tokens held by burn addresses, both read at the same block.
- Shibarium
- The Shiba Inu layer 2 network. Its gas token is BONE, and part of its base fees is turned into SHIB burns.
Related
More apps like this.
Top Memecoins by Market Cap and Chain
The largest memecoins ranked by market cap, with supply read from each token contract and the price source named on every row.
Multi-chainSolanaEthereum+2PEPE Coin Holders and Supply Tracker
How many wallets hold PEPE, how concentrated its supply is, what exchanges and team wallets hold and how much PEPE has been burned.
EthereumBONK Burn Tracker: BONK Burned, Supply and Holders
BONK burned each day from BONKbot fees, bonk.fun fees and BonkDAO votes, the mint's supply after every burn and how many wallets hold BONK.
SolanaMemecoin Monthly Report: Launches, Holders, Burns and Unlocks
Memecoins on-chain each month: launches and graduations by launchpad, holder changes in the largest coins, burns, unlocks and rugs.
Multi-chainSolanaBase+2New Crypto Tokens Launched Today
Tokens created in the last 24 hours that opened a DEX pool, with chain, launchpad, deployer, starting liquidity and holders.
Multi-chainSolanaBase+2Pudgy Penguins NFT Tracker: Sales, Floor, Holders and PENGU
Pudgy Penguins and Lil Pudgys sales, the low and median sale price, holders and PENGU holders on Solana, all read on-chain.
EthereumSolanaBuild Shiba Inu Burn Tracker: SHIB Burned by Day and Source on verified data.
Start free in Voltfin Studio: boards, tables and reports where every number opens its receipt. Tell us which data you need first and we will build it next.