Indexed ZilliqaBlockchain Data

Zilliqa’s mainnet has produced blocks since January 2019, and it was the first public network to split its validator set into shards rather than run every validator against every transaction. Shards produce micro-blocks, a directory-service committee orders them into transaction blocks, and the chain therefore advances on two counters instead of one. ZIL is the native token and pays gas. Contracts were originally written only in Scilla, a language designed for this chain in which a contract exposes typed transitions instead of Solidity functions, and ZRC-2 is its fungible token standard. The 2.0 protocol added a native EVM execution layer beside Scilla and moved block production to staked validators, so bytecode written for Ethereum now deploys here without displacing what came before. Accounts appear in two forms, a bech32 string beginning zil1 and a twenty-byte hex address, and both are one account.

SonarX indexes Zilliqa blocks, transactions and receipts, Scilla transition records and their events, decoded EVM logs, execution traces, and token transfers and balances from both execution layers. Those records land in the normalized model SonarX uses on every network it covers.

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 Zilliqa on request.

This history has two shapes. Scilla contracts emit records built from their declared transitions, so a decoder keyed to EVM log topics sees an empty chain where most of the older activity is, and the newer EVM layer has to be indexed beside it rather than instead of it. The sharded design adds a second clock: micro-blocks are produced per shard and combined into transaction blocks, so a query pinned to a height needs to know which height is meant. Addresses arrive in bech32 and hex forms for the same account, and both are resolved before balances are derived.

Token accounting is the first workload, and it is the one the two layers complicate: a holder can sit behind a ZRC-2 contract, an EVM contract, or both, and a supply figure has to reconcile them. Token analytics covers the issuance side across chains. Validator and reward accounting is the second, since staking rewards accrue as protocol state rather than as transfers. Contract-level research is the third, comparing what was built in Scilla with what has since been deployed in Solidity, which is a migration question a chain with one language never has to ask. Teams studying sharded networks usually pull Harmony alongside this one.

Tell us the delivery target, how far back you need and how fresh it has to be, and the share is scoped against that. Zilliqa 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.