Indexed Monad TestnetBlockchain Data

This is the public test network of Monad, running since 2025 and answering to chain ID 10143. It reproduces the parts of the protocol that matter to a data pipeline. Validators agree a block’s ordering under MonadBFT before the block is executed, execution then runs transactions in parallel and re-runs the ones that conflict, and blocks arrive faster than once a second, exactly as they do on the production chain. What differs is everything economic. Gas is paid in test MON handed out by a faucet, so balances and transfer amounts carry no market value, and the validator set is its own. The history is also not continuous: the network was reset from genesis on 16 December 2025, after mainnet went live on 24 November that year, so heights below the reset belong to a retired instance.

SonarX indexes this network the way it indexes any EVM chain: blocks and headers, transactions and receipts, event logs decoded against contract ABIs, execution traces including internal value transfers, and token transfers and balances. The same normalized model is used on every chain SonarX covers, so a query written here runs unchanged against a production dataset.

Full historical coverage is available today as a data-share or a file delivery. Real-time delivery is enabled on request. Balance tables and the balance APIs can be enabled for Monad Testnet on request. Kafka streaming can be enabled for Monad Testnet on request. How much history applies depends on the instance, which is confirmed when the share is scoped, and the coverage described here is for the test network rather than for mainnet.

The reset is the part that breaks naive pipelines. A genesis event partway through a network’s life means the same block heights recur with entirely different contents, so instance identity has to be part of the key rather than an afterthought, and a loader that appends by height merges two chains into one fiction. Deferred execution is the second consideration and is the reason this network earns a dataset: a header commits before its receipts exist, so SonarX tracks the execution frontier apart from the consensus frontier here exactly as it does on mainnet.

The workloads here are engineering ones. Pipeline rehearsal is the first and the most valuable, since a loader that assumes a header and its receipts arrive together will stall on this chain and it is cheaper to find that out on a test network. Throughput and cost testing is the second, sizing storage and query spend against a chain that produces blocks several times a second. Schema validation is the third, checking that decoded logs and traces land where a model expects before mainnet data is provisioned. Reset handling is the fourth, and it is the one no other kind of network can exercise. Berachain Testnet is indexed on the same terms.

Tell us the delivery target, how far back you need and how fresh it has to be, and the share is scoped against that. Say whether records from before the reset are in scope, because that decides whether you get one history or two. The published coverage matrix for every network SonarX indexes lives in the data documentation, and the rest of the catalogue is at all indexed chains.