Indexed StarknetBlockchain Data

Starknet is a validity rollup that has run on mainnet since 2021, built by StarkWare and settled on Ethereum. It does not run the EVM. Contracts are written in Cairo and executed by the Cairo VM, and execution is proved with a STARK proof that an Ethereum contract verifies, so a state update is accepted because it was proved rather than because nobody disputed it inside a challenge window. The account model is different as well. Starknet has no externally owned accounts: every account is a contract that validates its own transactions, which makes account abstraction the default rather than a wallet convention. Addresses are field elements rather than twenty-byte hashes, and contract code is declared as a class with its own hash before any instance of it is deployed. STRK is the network’s token and the asset transaction fees are paid in.

SonarX indexes Starknet blocks and headers, transactions and their execution results, Cairo events, contract declarations and deployments, and token transfers and balances. The same normalized model is used on every chain SonarX covers, so Starknet activity joins to EVM chains in one query rather than being reconciled between two pipelines afterwards.

Full historical coverage is available today as a data-share or a file delivery. Real-time delivery is enabled on request.

Nothing about Starknet decodes the way an EVM chain does. Events carry Cairo-encoded felt arrays, not ABI-encoded EVM logs, and the ABI that explains them belongs to a contract class rather than to an address, so decoding follows the class hash an address points at and has to move with it when the account or contract is upgraded. Because every account is itself a contract, a sender’s keys can rotate while the address stays fixed, which breaks the usual assumption that an address stands for a keypair. Token contracts are Cairo ports of familiar interfaces rather than the interfaces themselves, so transfers are normalized rather than read off a standard.

Account analysis is the first workload and the one that surprises teams. Because users hold funds in account contracts, counting users means resolving deployments and their owners rather than counting addresses that signed, which is the same problem wallet analytics solves across chains. DeFi research is the second: Cairo venues emit their own event vocabulary, so position and liquidity histories are built from decoded contract state instead of a shared log standard. Bridge reconciliation is the third, matching deposits and withdrawals against the messages Ethereum records, which is also how teams tie Starknet activity back to zkSync Era and other rollups in a single view. Fee analysis sits alongside them, since the cost of using Starknet is partly the cost of proving it, and that lands on Ethereum rather than here.

Tell us the delivery target, how far back you need and how fresh it has to be, and the share is scoped against that. Starknet history is available now, so a first delivery is provisioning rather than engineering. 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.