Overview
The chain as a full node on mainnet sees it, updated continuously.
Overlay traffic by broadcast kind
Everything accepted off the peer-to-peer overlay · scroll to zoom, drag to pan — each lane on its own
Message feed
Decoded from the transaction body using the official TON ABI catalog. Jetton names come from on-chain metadata via this node. Click a row for details.
How blocks arrive
Share of arrival events, not unique blocks: one block usually arrives more than once, by both paths
The life of a block inside a node
The three steps a block passes through before this node can use it, as the node times them itself. p50, with the p90 and how often each step fires behind it. Not every block takes every step: one that arrives by broadcast never needs fetching.
Block feed
Blocks as they close. Click one for its transactions.
Live shards
Basechain splits when a shard is loaded and merges when it is not. Each card is a shard producing blocks right now.
Bus throughput
Who holds the shard
Each chain is validated by a group that is reshuffled on a fixed clock. The catchain sequence number names the group holding it now; the bar is how far that group is through its turn. Group size is counted from the last complete turn, as the distinct validators that closed a block in it. Source: the chain's own block table.
Splits and merges
How many shards existed at each moment of the window. Every step is a real split or merge. Scroll to zoom, expand for the minute-exact record.
Who collates the blocks
Blocks by the dedicated collators registered in the validator registry, by other nodes that report collation telemetry, and the remainder — self-collated blocks that report nothing. Source: toncenter collation telemetry + the chain's block table. Follows the time window.
Storage-cache warmth
Warm-path storage read per block, p90, log scale. The dashed lines are the norm before 22 July and the cascade.
External messages per block
Externals a reporting collator received per block; the darker part was rejected.
Recent topology events
Newest first
Day by day
From this node's own minute-exact shard record: splits per day, share of the day spent on a single shard, and how long the merged topology held (median) — 115 s in the cascade, hours now. Independent of the time window.
Block production
Masterchain and shard block rate
Overlay traffic by broadcast kind
Hover any bar for the exact rate at that minute · scroll to zoom, drag to pan
Why broadcasts get dropped
Duplicates are counted apart from genuine rejections
What this node gives back
A full node is not only a consumer of the overlay. This is what it forwards on for other peers, against what it takes in.
Where broadcast time goes
Each stage a broadcast passes through inside this node, slowest first. p50 with the p90 behind it.
Reassembly in flight
Erasure-coded transfers being put back together
Plumtree
The gossip tree of overlay protocol v2. It is off on mainnet since 4 August, so these counters sit at zero — the zero is the measurement, not a gap. They will start moving the day v2 comes back.
Where the validators are
Every validator in the current cycle, placed by the geolocation of its announced address
No connection lines are drawn between sites: the node cannot attribute a broadcast to a peer (no peer IPs, no sender identity), so any route would be invented. Where a block is credited to a site, that is the validator whose leader window it was — with collators live it is not necessarily the machine that assembled the block.
Who produced the blocks
Every block names the validator whose leader window it was, in its own header. Counted straight from the chain's block table.
With collators live, the name in a block header is the validator whose leader window it was — not necessarily the machine that assembled the block. Per-block collator attribution is not observable.
Validators by hosting provider, per cycle
Each column is one validation cycle; the height is the whole active set, the colours are who hosts it. Provider of a node is taken from the latest network scan. Hover a column for the full breakdown; on a touch screen hold one instead.
Node software
Which build each validator runs, from public telemetry collected by toncenter. Click a version for the validators on it. The source and its last update are shown below; missing versions are never guessed.
Countries
Click a row for its validators, a header to sort
Hosting providers
Click a row for its validators — several providers per country is normal
Connect an agent
Read-only MCP over HTTP: the numbers, tables and chart posters this page shows.
https://mcp.tondevs.xyz/mcpclaude mcp add --transport http tondevs https://mcp.tondevs.xyz/mcpRun it in a terminal.
Tools
Click a name to copy it. Parameters marked * are required.
No tool matches this filter.