Indexed LineaBlockchain Data
Linea, the zkEVM rollup Consensys built on Ethereum, settles a batch when its proof verifies rather than after a challenge window, and its base fee sits on a floor of seven wei.
How to query Linea data with SonarX
Instant Data Share
Available todaySnowflake, and file dumps to your object storage
Query Linea 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 Linea 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 Linea 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 Linea 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 Linea activity within seconds
- Fraud and anomaly detection that has to fire before settlement
- Live dashboards and alerting on Linea 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
Enabled on requestTables and REST
Read what a Linea 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
- Real-time balances API for latest and historical balances
- Batch API for wallets, tokens and balances in bulk
Used for:
- Reconstructing Linea 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 Linea balances on page load
- Compliance checks that read one Linea 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 Linea 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 Linea data behind their own API layer
Linea data: frequently asked questions
What is Linea?
Linea is a zkEVM rollup on Ethereum, built by Consensys and open to the public since 2023. Transactions execute on Linea and are grouped into batches; a zero-knowledge proof covering each batch is then verified by a contract on Ethereum, which settles it. There is no challenge window, so settlement waits on proving rather than on a fixed dispute period. The execution environment is the EVM, so twenty-byte addresses, Solidity contracts and the usual tooling work unchanged, and a deployment can be mirrored from L1 with the same artifact. Gas is paid in ETH, and LINEA, issued in 2025, is a separate token that pays for no transactions. Fees behave unusually as a result: the base fee sits on a floor of seven wei, so almost all the variation in what a transaction costs is in the priority fee rather than in the base.
Linea 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 Linea activity can be compared with Ethereum and with the other rollups in one query rather than three.
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 Linea on request. Kafka streaming can be enabled for Linea on request.
How SonarX indexes Linea
The chain runs on two clocks and a pipeline has to carry both. Blocks are conflated, Linea’s own term for grouping several of them into one proven batch, and a batch settles only when its proof is verified on Ethereum. Every record therefore has a production time and a settlement time, so reporting that treats the L2 timestamp as final states as settled what is still in flight. The same split governs withdrawals, where the gap between the legs is set by proving cadence rather than by a fixed waiting period. Fee analysis needs its own adjustment, since a base fee pinned at a floor puts all the variation in the priority fee.
What teams build with Linea data
Two workloads account for most of it. Bridge and treasury reconciliation is the first: an institution holding assets on the rollup has to state a position that agrees with the L1 side, which means matching deposits and withdrawals to their settlement events rather than trusting a balance read at one moment. Position-level DeFi analytics is the second, built on decoded events and internal transfers, and it is inexpensive to extend from an existing Ethereum pipeline because the contract artifacts are the same. Protocol teams add a third: comparing user behavior on Linea with the same contracts on Ethereum or Scroll, where the interesting number is cost per action rather than raw counts. Fee research is a fourth and is unusual on this chain: with the base fee resting on its floor, what varies is what users chose to tip.
Getting Linea 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. Linea history is available now, with settlement events indexed alongside the blocks they finalize. 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 Linea data API?
Real-time and batch APIs over indexed Linea data are enabled on request: the same indexed dataset the Snowflake share reads, served over REST once provisioned. Tell us the lookup pattern you need.
How do I get Linea 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 Linea coverage go?
The historical data-share and file delivery cover the chain's recorded history from its 2023 public launch forward, and are available today. Real-time delivery keeps the same dataset current to chain tip and is enabled on request.
When is a Linea transaction settled?
When the proof covering it is verified on Ethereum, not when the block appears. Several Linea blocks are proven together, so a transaction is readable on the rollup first and settled on L1 some time later. Reconciliation work should key on the settlement event rather than on the L2 block timestamp, and the two can disagree by a meaningful margin near the chain tip.
Is Linea a rollup or a sidechain?
A rollup, and the difference is visible in the data. A sidechain has its own validators and its own security, and nothing about it is recorded on Ethereum. Linea posts its transaction data and its validity proofs to Ethereum, so every batch has a corresponding L1 record, which is what lets an analyst verify the rollup's history against the chain it settles on.