TINCBurn.fyi

龍炎 Methodology

← Burn tracker

方法 How the numbers are made

Every figure on the tracker is read from Ethereum. This page says exactly how.

燃焼 What counts as a burn

A burn is an ERC-20 Transfer event on the TINC contract whose recipient is the zero address (0x000…000). That is the event the token emits when TINC is destroyed, whether the buy-and-burn contract or anyone else triggers it. The scanner asks a dedicated Ethereum node for those events with eth_getLogs in chunks of 800 blocks, keeps the amount, transaction hash and sender of each, and groups them by the UTC date of their block. Transfers to other so-called dead addresses are not burns in TINC’s design and are not counted.

供給 Emission and supply

TINC is issued to Titan Farms liquidity providers at a fixed 1 TINC per second, 86,400 a day, and the protocol has no admin keys to change that, so the tracker uses the constant rather than re-reading it. Circulating supply is totalSupply() read from the contract at every update; burned TINC has already left it.

判定 The deflationary verdict

A day is deflationary when more than 86,400 TINC was burned in it. The 30-day figures compare the burns inside the window with 30 × 86,400 TINC emitted over the same days, and the net figure is the difference: supply grew when it is positive, shrank when it is negative. Days are UTC days, and the current day stays partial until it ends, so its bar can only grow.

龍階 Holders and Dragon Ranks

Wallet balances come from the same node: a snapshot of all holders, kept current by replaying Transfer events at each update. The two liquidity pools (TINC/TITANX 0x72e0…22e3 and 0xf899…0580) and the burn addresses are excluded, so a wallet that only holds TINC inside a pool position is not counted. Ranks are shares of circulating supply: Ryūjin 10% or more, Shōgun 1%, Daimyō 0.1%, Samurai 0.01%, Rōnin 0.001%, Ashigaru any balance above zero. “Total Warriors” is the number of wallets with a balance above zero after those exclusions.

更新 Freshness

The updater scans every 30 minutes and publishes every fourth run, so a new snapshot reaches the site about every two hours; the page itself regenerates within five minutes of a publish. The chip in the header shows the snapshot time, and “Cached” in the footer means the page served the last published snapshot rather than a live query. A burn confirmed a minute ago can therefore take one cycle to appear.

限界 Known limits

  • The tracker keeps a rolling 30-day window and no archive of earlier days; a day can be revised while it is inside the window, as the scanner recovers any block range the node failed to answer the first time.
  • Node outages leave gaps that are retried and backfilled; until then a day can read low.
  • Holder counts exclude TINC held only through liquidity positions.
  • Amounts are shown rounded; the JSON below carries full precision.
  • The tracker is independent of Titan Farms and reads public chain data only.

資料 Data and contracts