Indexed DymensionBlockchain Data

Dymension has produced blocks since February 2024, and its job is to settle for other chains rather than to run applications itself. Validators run CometBFT under proof of stake, DYM is the native token in adym units at eighteen decimals, and an account carries both a dym bech32 form and a twenty-byte hex form because the hub uses Ethereum-style keys. The chains it serves are called RollApps. Each one registers with the hub, appoints a sequencer that posts a bond, and publishes state updates describing the blocks it produced. Those updates are not final when they arrive: a window has to pass before the hub treats them as settled, and transfers leaving a RollApp wait with them unless a third party fronts the money for a fee. The hub runs pooled markets of its own as well, using the AMM module Osmosis wrote.

SonarX indexes what the hub commits: blocks and transactions with their typed messages, RollApp registrations and state updates, sequencer bonds and rotations, the finalization of each update, transfers held pending and the fulfillments that released them early, pool and liquidity records, staking and governance, and derived balances. Those records land in the normalized model SonarX uses on every network it 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 Dymension on request.

The records here describe other chains’ work, and the awkward part is time. A state update arrives, then a window has to elapse before the hub treats it as final, so a RollApp transfer has one height where it was created and a later one where it settled, and an analysis reading only the first reports money as arrived while it could still be undone. Early fulfillment adds a third party, because a market maker pays the recipient before finality and collects the original transfer afterwards, so the account that received the money first is not the one the transfer was addressed to.

Settlement monitoring is the first workload: which RollApps are publishing updates, how often, and how long finalization actually takes against the window it is allowed. Sequencer risk work is the second, tracking bonds, rotations and the periods where a chain had no active sequencer at all. Fulfillment economics is the third and is specific to this design, since the fee a market maker earned for fronting a transfer is a measurable price for time. Teams looking at where these chains put their block data pull Celestia into the same warehouse, and DeFi analytics covers the pooled-market side.

Tell us the delivery target, how far back you need and how fresh it has to be, and the share is scoped against that. Hub history is available now as a share or a file delivery, and streaming is provisioned on request. Say which RollApps matter, because the hub record and the chain record are scoped together. 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.