Indexed TezosBlockchain Data

Tezos launched on 30 June 2018 with a property no other chain of its generation shipped: it amends itself. Protocol changes are proposed, voted on and activated by the chain’s own bakers, without a client-coordinated hard fork, a route Cardano only opened years later, and each amendment carries a city name in alphabetical order beginning with Athens in 2019. Consensus is Liquid Proof of Stake, where bakers produce blocks and holders delegate their stake without giving up custody of it, and since the Ithaca amendment of April 2022 the algorithm has been Tenderbake, which finalizes a block two blocks after it is proposed. Successive amendments have also cut the block interval well below the sixty seconds the chain started with. Contracts run on the Michelson stack machine, typed and formally analyzable, with named entrypoints rather than selectors. The native asset is XTZ, divisible into a million mutez. Accounts come in two shapes: implicit tz1, tz2 and tz3 accounts that hold keys, and originated KT1 accounts that hold code and cannot sign for themselves.

SonarX indexes blocks and the cycles they sit in, operation groups and the operations inside them, transactions and the internal operations contracts emit, contract originations and calls with their typed parameters, delegation and baking records, token movements under the standard interfaces, and account balances. The same normalized model covers every network SonarX indexes, so Tezos activity lines up with other chains instead of arriving in a shape only this protocol uses.

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

The protocol under one block is not the protocol under the block before it, and that is the central problem. Amendments have added and retired operation kinds, changed cycle length and reward arithmetic, and altered the block interval, so every long-range metric has to be anchored to the protocol active at that level rather than computed against one schema. Underneath that, value moves in places a naive reader misses: an operation group is the signed unit but internal operations emitted by contracts are where much of the transfer volume lives, and baking rewards accrue as per-cycle ledger state rather than as operations anyone submitted.

Delegation and baking accounting is the first workload, and it is genuinely awkward without indexed history: rewards are cycle-level state, so what a delegator earned has to be rebuilt from cycle records rather than counted from transfers that were never made, across cycle lengths that changed under them. Digital-collectible analysis is the second, since Tezos hosts a large issuance ecosystem under the FA2 interface and mint, sale and royalty flows are contract calls with typed parameters. Treasury reconciliation is the third, restating XTZ and issued-token positions as at a date across implicit and originated accounts. Governance analysis is the fourth and rare: proposals, ballots and their outcomes are all chain records, so participation can be measured directly. Staking analytics covers the reward side across chains, and Polkadot is the usual comparison when the subject is upgrading without a fork.

Tell us the delivery target, how far back you need and how fresh it has to be, and the share is scoped against that. Tezos history is available now, and streaming is provisioned on request. Say which cycles or contracts matter, because that usually decides how many protocol eras a query has to cross. 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.