Indexed MultiversXBlockchain Data

MultiversX has produced blocks since its mainnet launch in July 2020, under the name Elrond until a rebrand in 2022 that changed nothing on the ledger. Its state is sharded: accounts are assigned to shards by address, several execution shards run in parallel, and a metachain coordinates them and records the notarized results. The protocol adjusts the number of shards to the validator count and the load rather than fixing it. Consensus is Secure Proof of Stake, which reaches agreement in two communication steps using modified BLS multi-signatures among a randomly chosen consensus group, and every epoch reshuffles up to a third of each shard’s validators to make collusion harder. Contracts compile to WebAssembly and run on the MultiversX WASM VM. EGLD is the native token, and accounts are bech32 strings with an erd prefix, unlike the sharded design on NEAR.

SonarX indexes the chain across its shards: blocks per shard and the metachain records that notarize them, transactions with their status and both halves of cross-shard movement, smart contract results, ESDT token issuance and transfers, staking and reward records, and derived account balances. Everything is normalized into the model SonarX uses across every network it covers, so a sharded history aggregates like a single-chain one.

Full historical coverage is provisioned for MultiversX on request.

Sharding decides everything about this pipeline. A transfer whose sender and receiver sit in different shards executes asynchronously, so its two halves appear in two shards’ blocks at different rounds, and a naive reading shows senders with no receivers. Ordering has to be reconstructed against the metachain rather than against any one shard’s height, because a shard’s block number is not a global clock. Reshuffling adds a second correction: validator membership of a shard is only true for the epoch it was measured in, so any attribution of blocks to operators has to be epoch-aware. Tokens are protocol-issued identifiers rather than contract addresses.

Reward and delegation accounting is the first workload, derived per epoch and per validator with commission netted out, which is the form auditors ask for, and staking analytics is where that sits as a solution area. Token accounting is the second, and the protocol-level token model makes it precise, since an ESDT identifier is assigned by the chain and cannot be confused with another contract’s asset. Throughput and cost research is the third, comparing what activity costs across shards over time. Teams studying sharded designs together usually hold TON in 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. MultiversX coverage is provisioned on request, so tell us the history depth and the delivery target and we will scope it. Say whether cross-shard pairing matters for your workload, because it changes how the backfill is built. 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.