Indexed X LayerBlockchain Data

X Layer is a ZK rollup on Ethereum, operated by the exchange OKX and assembled from the Polygon CDK, the same toolkit behind Polygon zkEVM. It has been on mainnet since 2024. Transactions execute on the rollup, batches are proved with zero-knowledge proofs, and a contract on Ethereum verifies each proof, which is what settles the batch; there is no challenge window, because settlement waits on proving instead. Execution is EVM-compatible at the bytecode level, so Solidity contracts and twenty-byte addresses port across unchanged. Gas is paid in OKB, an ERC-20 issued on Ethereum and bridged in, so the fee asset is the exchange’s own token rather than ETH. The network answers to chain ID 196, and the testnet that preceded it ran under a different name.

SonarX indexes X Layer end to end: blocks and headers, transactions and receipts, decoded event logs, execution traces including internal value transfers, and token transfers and balances, with batch and verification records identifiable beside them.

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 X Layer on request. Kafka streaming can be enabled for X Layer on request.

The fee asset is the first adjustment. Gas is charged in OKB, whose supply lives on Ethereum, so a cost series here is denominated in an asset that also moves on the L1, and comparing it with an ETH-priced rollup needs a conversion the records do not carry. Proving cadence is the second: a batch is sequenced, proved, then verified on Ethereum, so a transaction is readable well before it settles and a reconciliation keyed on the L2 timestamp calls finished what is still in flight. It inherits the CDK’s batch shapes, so its L1 side reads the way Polygon zkEVM’s did.

Token accounting on OKB is the workload this chain adds. The asset pays for gas here, is issued on Ethereum and moves between the two, so supply, distribution and spend hold together only when both chains are read against each other. Lending and perp positions rebuilt from decoded events are the second, which is where DeFi analytics work sits. Flow analysis is the third, following capital between the exchange’s chain and the rest of the ecosystem, where the useful question is what arrives and what leaves rather than what sits still. Settlement research is the fourth and belongs to ZK rollups specifically: how long a batch takes from sequencing to verification, which is what a Scroll comparison actually measures.

Tell us the delivery target, how far back you need and how fresh it has to be, and the share is scoped against that. X Layer history is available now, with proof-verification records kept beside the blocks they settle. 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.