Indexed AptosBlockchain Data

Aptos has produced blocks since October 2022, and it descends from Diem: the Move language, the BFT consensus and much of the framework came out of that project. Validators run AptosBFT under proof of stake, and a committed block is final, so there is nothing to unwind and no confirmation depth to count. APT is the native token, divisible into a hundred million octas, and addresses are thirty-two bytes. Where Sui made objects the primitive, Aptos kept accounts and put typed resources under them: a balance is a field inside a resource stored at an account address, and a module’s state lives wherever its resources are held. Execution is parallel through Block-STM, which runs transactions optimistically and re-executes the ones that conflict, so a block’s transactions are ordered without being processed in single file. Two numbering systems coexist. Every transaction carries a global ledger version and a block groups those versions, so height and version are different axes through the same history.

SonarX indexes Aptos in the shapes the framework produces: blocks and their transactions, state changes at the resource level, module publications, typed events, coin and fungible-asset movements, staking and delegation records, and derived balances. Everything is normalized into the model SonarX uses across every network it covers, so an Aptos holding and an EVM holding can be compared without rewriting the query for each.

Full historical coverage is available today as a data-share or a file delivery. Real-time delivery is enabled on request. Kafka streaming can be enabled for Aptos on request.

Three Aptos-specific problems turn up in every project. Balances are not a ledger table: they are fields inside typed resources under an account, so a holder view means reading the right resource type, and the same asset can sit in a coin store and in a fungible-asset store at once, which double counts if both are summed. Events are the second, because older streams are tied to handles with their own counters while newer ones are emitted by modules directly, and a complete series needs both resolved into one. Numbering is the third, since a join on block height and a join on ledger version are not the same join and mixing them loses transactions at the edges.

Custody and exchange reconciliation is the first workload, and it stands or falls on resolving the two token representations, because a report that counts a coin store and a fungible-asset store for the same asset states the position twice. Reward and delegation accounting is the second, derived from staking state per epoch rather than from transfers, and staking analytics covers that shape of work across chains. Token distribution analysis is the third, following an asset from minting to the accounts that still hold it. Application analytics is a fourth, built from typed events, which is cleaner than log decoding as long as both event generations are handled. Teams comparing parallel-execution designs usually pull Solana into the same warehouse.

Tell us the delivery target, how far back you need and how fresh it has to be, and the share is scoped against that. Aptos history is available now as a share or a file delivery, and streaming is provisioned on request. If asset-level accuracy matters more than raw activity, say so, because that decides how the two token standards are reconciled. 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.