Stats from your validation session, and the feed configuration the Blocks page uses. Everything
stays in your browser — nothing is sent anywhere.
Session stats
—
chain tip
—
blocks in window
—
blocks this session
—
transactions decoded
—
block data decoded
—
blocks cached
—
served from cache
—
feed age
—
Datacarrier breakdown
OP_RETURN outputs across the current window, by class. What are these? →
No data yet.
Datacarrier — all-time, across your cache
OP_RETURNs over the 80/83-byte standard, by protocol, across every block you've cached.
No cached history yet.
Feed & source
Which NIP-333 publisher and relays the Blocks page follows. Changes apply when the Blocks page reloads.
saved ✓
Local node — roadmap
Where this is heading: from a live viewer into a self-sufficient node that needs no block API.
Cache blocks locally
Persist validated blocks in your browser (OPFS) so they aren't re-fetched from a block API. Runs as a pruned node: oldest blocks are evicted beyond the budget below. Applies when the Blocks page reloads.
—
Full validation from a snapshot later
Maintain a UTXO set and validate every input (prevouts, scripts, fees) — the current page validates structure + context only.
Peer over WebRTC experimental
Fetch blocks directly from other browsers (and serve yours) over a WebRTC mesh — trustless, every block verified by hash. In the fetch path: local cache, then a peer, then the explorer as fallback. Set a signaling server to enable; applies when the Blocks page reloads.