the ledger, walkable — every number shows its source row, every page its commitment root
| /explorer/kat | supply, sinks, service columns, the RATIFIED genesis row, live params vs genesis |
|---|---|
| /explorer/account/<id> | one account: balance, grant, burn watermark + event log, credit events, receipts, and the pre-event-log residual. A full 32-hex id or an 8-hex 4+4 prefix both work; an ambiguous prefix gets a pick list. Pages render only 4+4 — pseudonymous by construction. |
| /explorer/epoch/<n> | the settle row, epoch split params (+ drift vs genesis), the committed telemetry row incl. stats_root, hourly burn-settle buckets |
| /explorer/stake/<id> | one staking position: USDC/KAT tranches with unlock dates, unstake requests (escrow + vent schedule), KAT redeems, accrued, the per-epoch distribution markers |
| /explorer/gov[/<id>] | governance: the proposal list (kind, state, timeline ticks, tally), per-proposal votes, applied param intents, ban rows; <id> opens one proposal's detail |
| /explorer/nft | the item shop's catalog (prices, stock, editions, denominations) + the art listings (owner, creator royalty, sale trail) + the shop's burned-total stats |
| /explorer/mining | the mining reward LEDGER half: proven reward rows by epoch (weight, paid), the unpaid queue; the ingest/queue half links out to /mining/* |
| /explorer/fixstats | the committed work-stats fold: per-epoch stats_root commitments + the verify links; live counters link to /mining/fixstats |
| /explorer/payreq/<32hex> | one payment request: kind, state timeline, pinned amount, the settled invoice when the KAT rail settled it |
| /explorer/live | the recent-events feed: an honest MERGE of the globally orderable sources (deposits, burn-settle buckets, governance proposals, mint receipts, epoch boundaries) — labeled per plane, capped, and explicit about the per-account logs it cannot see |
| /explorer/genesis | genesis vs live: the deployed kat:cfg:v1 row vs the compiled defaults (each row labeled NEVER-LEVER), the live EpochParams levers vs their governance bounds, the applied param intents, and the RATIFIED pointer |
| ?format=csv | the table views export CSV: gov list, NFT catalog, mining rewards — same rows as the JSON twin, header row, RFC-4180 quoting, 4+4 ids (D2) |
| /explorer/search?q= | one box: account (8-hex 4+4 prefix, full 32-hex service id, or the client's full 64-hex local id — the ledger keys its first 32 hex), receipt id, epoch number, acct:seq |
Every page has a JSON twin: ?format=json (or any non-www host). Amounts are integer micro + the rendered KAT string. The traceability chain: genesis → grant → burn report → watermark → hourly settle → epoch split → receipt → vest → spend.
verify: no stats_root committed yet · /mining/statroot