Indexed MantleBlockchain Data
Mantle is the Ethereum Layer 2 that prices gas in MNT, and it replaced its own security model in place, moving from optimistic fraud proofs to zero-knowledge validity proofs without resetting the chain.
How to query Mantle data with SonarX
Instant Data Share
Available todaySnowflake, and file dumps to your object storage
Query Mantle blockchain data with plain SQL from a live database inside your own Snowflake account, populated with the indexed chain dataset. There is no pipeline to build and no second copy to store. The same dataset ships as file dumps to your own object storage for lakes and warehouses that are not Snowflake.
- Full history as a Snowflake data-share
- File dumps to S3 or your own object storage
- Real-time delivery, current to chain tip — on request
Used for:
- Analytics teams already on Snowflake that want Mantle data beside their existing tables
- Fund accounting and treasury reporting that reconciles against a fixed history
- Cross-chain questions answered in one SQL statement instead of one query per chain
- Loading Mantle history into BigQuery, Databricks, Redshift or a Spark lake
- Replacing a self-hosted indexer and the engineering time that keeps it running
- Serving one governed dataset to several desks without copying it per team
Kafka Streaming
Enabled on requestEvent stream
Consume Mantle activity as a continuous stream of normalized records, produced as the chain is indexed instead of polled for.
Used for:
- Trading and execution systems that act on Mantle activity within seconds
- Fraud and anomaly detection that has to fire before settlement
- Live dashboards and alerting on Mantle wallet or protocol activity
- Feeding a stream processor that already reads from Kafka
- Keeping an internal store hot without waiting for a batch window
- Event-driven services that would otherwise poll on a timer
Balances
Available todayTables and REST
Read what a Mantle address held, either as it stands now or exactly as it stood at a past block or timestamp.
- Point-in-time balance tables, as at any block or timestamp — on request
- Real-time balances API for latest and historical balances
- Batch API for wallets, tokens and balances in bulk
Used for:
- Reconstructing Mantle portfolios and NAV as at a reporting date
- Audit and reconciliation work that has to be repeatable months later
- Wallet and portfolio products that render Mantle balances on page load
- Compliance checks that read one Mantle address at one block height
- Refreshing holdings for a whole book of accounts on a schedule
- Tax and cost-basis workflows that need holdings at each event
Realtime API
Enabled on requestREST over the indexed dataset
Query indexed Mantle records over REST, reading the same dataset the share reads, with no warehouse in the path.
Used for:
- Applications that need one answer rather than a table scan
- Customer-facing screens where query latency is visible to a user
- Services that have no data warehouse and do not want to run one
- Prototyping against production data before committing to a share
- Backend checks that run per request instead of per batch
- Teams that want indexed Mantle data behind their own API layer
Mantle data: frequently asked questions
What is Mantle?
Mantle is an Ethereum Layer 2 that has been producing blocks since 2023 and is the successor to BitDAO, whose treasury and BIT token moved across to the network and to MNT. Two things separate it from the rest of the L2 field. Gas is paid in MNT rather than ETH, so transaction cost is denominated in a token that moves against the asset Ethereum charges the chain in, and the protocol carries an oracle ratio to convert between the two. And the chain has replaced its security model in place: it launched on the OP Stack as an optimistic rollup with a seven-day challenge period, and now settles with zero-knowledge validity proofs, which cut withdrawals to hours. Execution is the EVM throughout, with the usual twenty-byte addresses. Data availability has moved as well, from a separate availability layer to Ethereum blobs, and none of it reset the chain: block numbering runs unbroken from the first block.
Mantle data on SonarX
SonarX indexes blocks and headers, transactions and receipts, event logs decoded against contract ABIs, execution traces including internal value transfers, and token transfers and balances. The same normalized model is used on every chain SonarX covers, so Mantle sits beside the ETH-gas rollups in one dataset despite pricing its own fees differently.
Full historical coverage is available today as a data-share or a file delivery. Real-time delivery is enabled on request. The real-time balances API and the batch wallets, tokens and balances API are available for Mantle, and the rest can be enabled on request. Kafka streaming can be enabled for Mantle on request.
How SonarX indexes Mantle
This chain is several protocol regimes stitched into one history, and the seams are where numbers go wrong. Early blocks carried a single transaction each and arrived at irregular intervals; later ones hold many and land on a fixed cadence, so any rate computed per block changes meaning partway through. Gas accounting shifted too: for much of the chain’s life the reported gas figure folded in an amortized share of L1 cost, which makes those values incomparable with other rollups and with Mantle’s own later blocks. Data availability moved twice before settling on Ethereum blobs, so reconstructing the earliest batches from L1 alone does not work. SonarX normalizes across all of it.
What teams build with Mantle data
Cost accounting comes first here and is genuinely different from the rest of the field. An application’s spend is in MNT, the comparison is usually against a chain that charges in ETH, and stating either in one currency means carrying a conversion and being explicit about it. Position-level DeFi analytics is the second workload, since the protocols on the chain hold balances in both MNT and bridged assets and a position’s value depends on which is which. Bridge and treasury reconciliation is the third, matching what left Ethereum against what arrived, which is the same exercise a team runs on Blast and every other rollup, with a second asset in the middle. Transaction monitoring runs on the same indexed tables.
Getting Mantle data from SonarX
Tell us the delivery target, how far back you need and how fresh it has to be, and the share is scoped against that. Mantle history is available now, with the fee fields from each era normalized into one model. 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.
Is there a Mantle data API?
Yes. Real-time and batch APIs over indexed Mantle data are available today, covering historical and latest balances and wallet, token and balance lookups in bulk. They read from the same indexed dataset as the Snowflake share and the file delivery, so an API answer and a warehouse query agree.
How do I get Mantle data into Snowflake?
SonarX provisions a data-share into your own Snowflake account. The share appears as a database you query with SQL, so there is no pipeline to build and no second copy to store, and it stays current as SonarX advances the indexing pipeline.
How far back does Mantle coverage go?
The historical data-share and file delivery cover the chain's recorded history from its first blocks in 2023 forward, and are available today. That history spans several protocol eras, with different block structures and different data availability arrangements, all normalized into one continuous record. Real-time delivery keeps the same dataset current to chain tip and is enabled on request.
How does paying gas in MNT change fee analysis?
It adds a conversion to every question about cost. Fees are denominated in MNT while the L1 charges the chain in ETH, so the protocol carries an oracle ratio between the two, and any cost stated in ETH or dollars is a derived number rather than a reading. Comparing an application's cost here with the same application on an ETH-gas rollup means fixing which price series you are converting through.
Is Mantle still an optimistic rollup?
No, and the change is recent enough that most reference material is out of date. Mantle launched on the OP Stack as an optimistic rollup and later moved to zero-knowledge validity proofs, retaining an optimistic route as a fallback. Its data availability also moved from a separate availability layer to Ethereum blobs, so Ethereum now carries the full record where for part of the chain's life it did not.