Indexed GravityBlockchain Data

Gravity launched in 2024 as the Gravity Alpha Mainnet, an Ethereum rollup built on the Arbitrum Nitro stack with chain ID 1625, and it now runs as an L1 in its own right: Gravity Mainnet, chain ID 127001, with an AptosBFT-derived consensus and a parallel EVM execution engine. The native asset is G, divisible to eighteen decimals, and it pays for gas on both. The chain also carries a native oracle at the protocol level rather than as a set of contracts, and its remit is wider than prices: it can attest to state from other chains, to DNS records, and to the JWK providers behind keyless authentication. Execution is account-based over twenty-byte addresses, and Solidity contracts deploy unchanged, which is why the rollup’s applications moved across. The Nitro stack still shapes how the earlier records read.

SonarX indexes Gravity blocks and headers, transactions and receipts, decoded event logs, execution traces including internal value transfers, and token transfers and balances, in the normalized model used on every chain SonarX 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 Gravity on request. Kafka streaming can be enabled for Gravity on request.

This network’s history is not one sequence. The rollup years were produced by a sequencer and settled to Ethereum, while the current chain reaches finality in its own validator set, so block numbering restarts and the meaning of a confirmation changes at the boundary. Parallel execution matters at the same seam: transactions that a serial chain would order one way are committed concurrently, and a trace has to reflect the order the execution engine actually used rather than an assumed one. The protocol oracle adds a third stream, since price and external-data updates arrive as protocol activity rather than as user calls.

Cross-chain address accounting is the workload this network creates: stating what an address holds and did means lining up two ledgers with different block numbering, and a single balance answers neither question. Token-distribution analysis is the second job, because campaign and reward payouts here land as large batches of small transfers that only aggregate usefully in bulk. Position-level DeFi analytics is the third, built from decoded events and internal transfers. Teams benchmarking parallel execution designs usually read this chain beside Monad.

Tell us the delivery target, how far back you need and how fresh it has to be, and the share is scoped against that. Say which of the network’s chains your reconciliation covers, since the two are numbered separately, and the share is built to match. 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.