Indexed SuiBlockchain Data

Sui’s mainnet has been running since May 2023, and the shape of its state is what makes it unusual. There are no accounts holding balances and, strictly speaking, no blocks: the ledger is a set of objects, each with an identifier, a version and an owner, and transactions are sequenced into checkpoints rather than gathered into blocks. A transaction’s result is expressed as the objects it created, mutated, wrapped or deleted. Contracts are Move packages, and coins are objects as well, so a wallet’s balance is the sum of the coin objects its address owns rather than a row in a table. SUI is the native token, divisible into a billion MIST, and addresses are thirty-two bytes. Validators run Mysticeti, a BFT protocol built over a directed acyclic graph, under delegated proof of stake, with the validator set fixed for the length of an epoch. Transactions touching different shared objects execute in parallel across cores, so throughput here comes from independence between transactions rather than from larger blocks.

SonarX indexes Sui as the object graph it is: checkpoints and the transactions inside them, the object changes each transaction produced, Move package publications and upgrades, typed events, coin and token movements, staking records, and the balances derived from the objects an address owns. Everything is normalized into the model SonarX uses across every network it covers, so a question about holdings here takes the same form as on an account-model chain.

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

An indexer for this chain follows object versions, not account diffs. Each transaction reports the objects it created, changed or destroyed, so a position at a past date means replaying that history to the versions an address owned then. Coins compound it: they are objects that split and merge, so a balance is an aggregate over a set whose shape changes even when its total does not. Programmable transaction blocks put several commands under one digest, so one transaction is often many logical actions. Packages are immutable, which means an upgraded application appears at a new address and its history spans both.

Portfolio reconstruction is the first workload and the one the object model complicates most, since holdings as at a date have to be assembled from the coin objects an address owned then rather than read from a balance field. Provenance work is the second, because digital assets are objects with owners and versions, so an item’s whole custody history is in the record. Wallet analytics covers the identity side of that across chains. Reward and delegation accounting is the third, derived per epoch rather than from transfers. Application analytics is a fourth, and it needs package upgrades resolved, or an app’s history breaks at every new version. Teams working across the Move ecosystem pull Aptos into the same warehouse, often beside Solana.

Tell us the delivery target, how far back you need and how fresh it has to be, and the share is scoped against that. Sui history is available now as a share or a file delivery, and streaming is provisioned on request. Say whether object-level detail or address-level positions matter more, because that changes the backfill. 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.