MSG Chain
Access blocks, transactions, receipts, and validator status, plus the stricter explorer boundary notes carried by the whitepaper.
The public explorer is still being rolled out in stages. The whitepaper already covers how contract, source, log-filtering, and hash-search checks behave locally when validation fails, along with the related proof chain.
Block height, transaction hash, receipts, validator rotation, gas usage, contract-source metadata, canonical source views, and the boundaries of hash search and log filtering.
The whitepaper now explains explorer-facing query capabilities such as receipt replay, `source=canonical`, `eth_getLogs`, WebSocket log filters, and how hash search returns a failure instead of guessing when a lookup cannot be confirmed. Public rollout is still being staged.
Use the whitepaper system to connect public explorer expectations with the stricter explorer module, the indexer data layer, how the hash index behaves when a lookup cannot be confirmed, and the proof map.
Explorer Module Proof MapDevelopers, bots, and RAG services can read machine metadata from explorer exports, chunk indexes, and indexer data-retention rules before deciding how to connect production endpoints.
Explorer Export Chunk Index