BAT: Supply Burned by Route [BAT]
Shown as its 2019–2022 sample; the latest readings and full history are included with Plus.
BAT burned in each period, split by how it was burned.
Why use it. Separates burns that lower the token's recorded total supply (its own burn function) from tokens parked at burn addresses, which still count in the contract's totalSupply() although they can never move. How to read it. The routes stack to Supply Burned.
Calculation. Sent to the Zero Address: transfers to the zero address. Sent to 0x…dEaD or 0x…01: transfers to those two addresses. Burned means sent to an address from which tokens can never move again: the zero address (a transfer there is the token's own burn and lowers its total supply), 0x000000000000000000000000000000000000dEaD and 0x0000000000000000000000000000000000000001. A transfer out of such an address would count as negative (none has moved anything). Not counted: tokens sent to other addresses that may be unspendable (for example 0xffffffffffffffffffffffffffffffffffffdEaD or vanity addresses that start or end in dead), tokens locked in contracts, and burns of copies of the token on other networks. BAT's contract has no burn function and accepts plain transfers to the zero address: tokens sent there stay in its fixed total supply of 1.5 billion, held by that address, but can never move again, so they count as burned here (533,838 BAT by 8 November 2026, equal to the zero address's balance on our node). Computed by CryptoKeyhole from every Basic Attention Token token transfer recorded by its own Ethereum archive node since the token's creation in May 2017, finalized blocks only; amounts are exact until they are published. Periods are UTC; a day is the sum of its hours (amounts) or its last hour (totals), and the open day is shown as a labelled partial.