Bittensor, measured.
Public, source-linked Bittensor data for people—and the same registry for agents.
Network allocation
Latest daily emission.
Live explorer
Latest blocks.
Newest at left. Refreshes while this tab is open.
Emission gains. Which subnets gained daily alpha during the selected window.
Loading 30d emission comparison · chain-derived snapshots
Chain activity. Daily totals across complete UTC days.
- Blocks
- Loading Blocks
- Extrinsics
- Loading Extrinsics
- Events
- Loading Events
- Head block
- Loading Head block
Loading complete-day chain activity · indexed chain data
Health. Which public surfaces need attention.
- Subnets at 99%+
- Loading Subnets at 99%+
- Probed
- Loading Probed
- Lowest uptime
- Loading Lowest uptime
Loading 7d surface health · live prober
Why a registry and not just an explorer
Chain explorers show state: stake, emission, blocks. They cannot tell you whether a subnet's API is reachable, what schema it speaks, or where its documentation lives — that is application-layer information, and it lives off-chain. Metagraphed catalogues it, verifies it against the operator's own sources, and serves the result as JSON, GraphQL, MCP tools and CSV as well as these pages.
What you can rely on
Identity comes from on-chain metadata and operator-published sources; health comes from our own probes; anything we could not verify is marked rather than guessed. Absence is stated explicitly instead of rendered as a zero, because a missing measurement and a measurement of nothing are different facts.