Indexed Kinto TestnetBlockchain Data

This is the public test network of Kinto, an EVM rollup built with the Arbitrum Nitro stack, and it answers to chain ID 42888. Gas is paid in test ETH rather than in a token of its own, which is why no native asset is listed for it. It exists to rehearse rules with no equivalent on a general-purpose chain. Externally owned accounts are disabled on the Kinto network, so a user acts through a non-custodial smart-contract wallet under EIP-4337 and the wallet contract, not a key, is the account of record. Transacting also requires a verification token held by the sender, enforced during execution rather than by an application, so an unverified sender simply reverts.

The mainnet network’s operators have published a closing plan, so whether this network still produces blocks is worth confirming with us. Either way, the recorded history is what SonarX indexes.

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 records here take the same shape as production records.

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 Kinto Testnet on request. Kafka streaming can be enabled for Kinto Testnet on request. Depth is confirmed when the share is scoped, and the coverage described here is for the test network rather than for mainnet.

Nothing on this network looks like an ordinary transaction trail. Because keys cannot transact directly, the sender recorded against an operation is the infrastructure that submitted it, and the account that authorized it sits inside the wrapped call. Attribution therefore means decoding that call, resolving it to a wallet contract, and reading factory deployments to know which addresses are user accounts at all. Identity gating adds a second dimension: permission to transact can be revoked, so an address can hold a balance it cannot move. Test deployments are also rebuilt, so the instance a record belongs to matters.

The work is engineering rather than analysis. Decoder development is the first case: building the logic that turns a bundled operation into an attributed user action, and checking it against records where every transaction takes that form. Integration testing is the second, for teams whose transfers must satisfy a permission check before they settle. Schema validation is the third, confirming that traces and decoded logs land where a model expects. Account-abstraction research is the fourth, since this history is a rare public record of sponsored, gated transactions. Monad Testnet is indexed on the same terms, and Arbitrum is the reference for the stack underneath.

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 wallet-factory deployments should be resolved to account owners, because that is far easier to set at scoping time. 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.