stats_

the standing rules

server-rendered on purpose: these hold whether or not the frame above loaded, and they are the claims you can hold us to.

• Every number on this terminal is a MEASUREMENT, never a verdict. There is no SAFE badge, no score, no rating, no recommendation copy, and no paid placement anywhere — appearing on a surface means a measurement crossed a stated threshold, nothing more.
• A failure renders as a failure. When an RPC call, a database read or a fetch does not answer, the surface says OUR read failed — it is never dressed as “this token has no volume”, “this wallet holds nothing” or “this chain is quiet”.
• Stale renders as stale, with its timestamp. Every figure carries its window; a window our coverage does not fill is disclosed as partial; a sum that can only undercount is called a floor.
• Token identity is decoration. Symbol, name and image are written by the token deployer; they are sanitised before rendering and they order nothing, colour nothing, gate nothing. The only unforgeable thing on a row is the address.
• Unknown says UNKNOWN. A cost basis we did not witness, a decimals() that did not answer, a depth that cannot be read — each renders as unknown or unmeasured, never as 0 and never as a guess.
• Aggregated timeframes say so. Candles are stored at 5-minute grain; every coarser chart is aggregated from 5m and labelled as such. There is no 1-minute data, and no surface pretends otherwise.

how the machine actually measures

the mechanics, because “trust us” is not a measurement — each of these cost real hours against the live chain and each is checkable.

• This chain's RPC ignores `topics` filters on log queries, so the walker decodes EVERY log an address emits and checks what it is — filtering happens in our code, never on trust that the server filtered.
• getLogs answers roughly 2,000 blocks per call here. The walker chunks, bisects on failure, and spends a per-tick call budget — when the budget bites it drops the tail and counts the shortfall rather than silently narrowing the window.
• The chain runs ~10 blocks a second, so every window is measured in TIME, never in blocks alone.
• No working V3 quoter exists on this chain — the canonical addresses have code and return empty. V2 and V3 prices are derived from pool state (reserves; slot0 + liquidity) instead, and no figure anywhere came from a quoter that does not work.
• Uniswap V4 is a singleton PoolManager: per-pool token reserves are not readable as balances, so a V4 depth figure renders as unmeasured — never 0, never a guess.
• V4 swap amounts are the swapper's deltas; V3's are the inverse. The decoders keep the two sign conventions apart, because reading one as the other inverts every buy/sell label on the tape.
• Candle prices are stored decimals-free — wei per raw token unit — so a failed decimals() read can never silently rescale a stored series. decimals stays NULL until the contract answers, never defaulted to 18.
• Trader attribution is the transaction signer (tx.from), resolved from full blocks. The swap event's sender on this chain is essentially always a router or launchpad contract — measured live: 0 of 1,974 sampled swaps had sender equal to signer — and ranking senders would be a list of routers wearing a whale costume.

The raw frame this page renders is public at /api/v1/chain/stats; index liveness at /api/health/chainwide. Most new tokens on this chain go to zero. Scan before you buy.