Linea Data: Index zkEVM Contracts, Tokens, and Decoded Transactions

Index Linea's zkEVM contract events, token transfers, and decoded transactions in one pipeline, delivered to your own database. Real-time and complete historical data, no node to run.

Linea is a zkEVM Layer 2 built by Consensys, the team that created MetaMask, and it frames itself with a single line: Linea is Ethereum. In September 2026 Consensys split into two companies, MetaMask and a new Consensys, with Linea moving to the new Consensys. Linea is a bytecode-equivalent zkEVM that batches transactions off-chain, generates zero-knowledge validity proofs, and posts them to Ethereum for verification, so Solidity contracts deploy with the same bytecode, ABI, and tooling you already use on L1. ETH is the only gas token, and the network is designed to strengthen the ETH economy rather than route around it. You can read how the team frames it at linea.build.

What makes Linea interesting is also what makes it noisy. It runs an aggressive throughput roadmap and carries a dual-burn fee mechanism that ties activity back to both ETH and the LINEA token. Indexing Co covers Linea in a single pipeline, decodes the raw chain into the shape you want, and delivers it to your own PostgreSQL, warehouse, or webhook. Real-time and full history, with no node to operate.

Source Linea zkEVM blocks

Ingest blocks, logs, traces

Decode ABIs to events

Transform your JavaScript

Deliver your database

Why Linea data is hard

zkEVM L2 Settlement Shape Linea is a validity rollup: the sequencer orders transactions, a prover compresses them into zero-knowledge proofs, and batches settle on Ethereum L1. Bridge deposits, message passing, and the proof-backed finality lifecycle add structure that a plain EVM scraper never sees. You want history that reflects how the rollup actually settles, not just block-by-block logs.

Throughput Headroom Linea's throughput roadmap has pushed sequencer capacity past 100 mGas/s. Capturing swaps, mints, and wallet activity in real time without falling behind the chain head is a standing engineering problem rather than a one-time backfill.

EVM Decoding Across Protocols A real Linea dataset spans many contracts at once: Uniswap v2, v3, and v4 pools, lending markets, and a long tail of consumer apps. Each needs its own ABI and event handling, and proxy upgrades keep the correct ABI a moving target as contracts evolve.

Fee Mechanics and ETH Burn ETH is the sole gas token on Linea, and its dual-burn design routes a share of fees into permanent ETH and LINEA burns. Reconstructing fees, burn flows, and gas accounting correctly means tracking the network's own economics rather than assuming a generic L1 fee model. Naive assumptions drift your numbers.

What Indexing Co delivers for Linea

The DIY Path

Stand up and maintain the whole stack yourself.

Run a Linea archive node or wire up a third-party RPC.
Fetch and decode logs, traces, and receipts against the right ABIs.
Track proxy upgrades and per-protocol event schemas by hand.
Build backfill, reorg handling, and real-time delivery from scratch.

Indexing Co

One pipeline sources, decodes, and delivers Linea to your store.

Linea contract events, token transfers, and decoded txs in a single pipeline.
Decoded data, shaped by your JavaScript transform.
Lands in your PostgreSQL, BigQuery, warehouse, or webhook.
Real-time delivery plus complete backfilled history. No node, no RPC babysitting.

What you can index

EVM data type	On Linea, for example
Contract events and logs	Uniswap v3 and v4 swaps, lending market borrows
Token transfers (ERC-20, ERC-721)	ETH-denominated transfers, stablecoin payments, NFT mints
Decoded transactions and traces	Wallet activity, bridge deposits and withdrawals
Protocol and account state	Pool reserves, lending positions, vault balances

A transform, not a subgraph

You write the transform in JavaScript, not AssemblyScript, and change it without re-indexing from block zero. Indexing Co runs your function over each block server-side: decode the logs you care about and return rows for your destination.

// Indexing Co transform: reshape each block into rows for your database
function transform(block) {
  const results = [];
  const signatures = [
    'event Transfer(address indexed from, address indexed to, uint256 value)'
  ];

  for (const tx of block.transactions || []) {
    for (const log of tx.receipt?.logs || []) {
      const event = utils.evmDecodeLogWithMetadata(log, signatures);
      if (!event) continue;
      results.push({
        chain: block._network,
        block: Number(block.number),
        tx_hash: tx.hash,
        contract_address: log.address?.toLowerCase(),
        from: event.decoded.from,
        to: event.decoded.to,
        value: event.decoded.value,
      });
    }
  }
  return results;
}

Linea with Indexing Co

Run it yourself if

You want full control of node infrastructure and have the team to operate a Linea archive node, decode every protocol's ABIs, and build backfill and reorg handling in-house.

Use Indexing Co if

You want Linea contract events, token transfers, and decoded transactions delivered to your own database, with real-time plus complete history and no infrastructure to run.

Get a Demo Open the Console

FAQ

Do I need to run a Linea node?

No. Indexing Co sources Linea blocks, logs, and traces for you, including full historical data, so you never operate an archive node or babysit an RPC endpoint.

Can I index any protocol on Linea?

Yes. Point a pipeline at any Linea contract or set of contracts, from Uniswap and lending markets to your own deployments, and we decode the events against the right ABI.

Does Indexing Co handle Linea's zkEVM settlement and proxy upgrades?

Yes. Because Linea is a zkEVM that is bytecode-equivalent with the EVM, standard ABI decoding applies, and the pipeline tracks proxy implementation changes and rollup batch settlement so your decoded data stays correct as contracts upgrade.

How does Indexing Co handle Linea gas and fee data?

ETH is the sole gas token on Linea, and we account for its fee accounting and dual-burn mechanics so your gas, fee, and timestamp fields stay accurate rather than drifting on generic L1 assumptions.

Can I get complete historical Linea data?

Yes. We backfill from your chosen start block and merge it with real-time data, so your Linea dataset is gap-free from genesis forward if you want it.

Get Started

Index Linea in minutes. Set up your first Linea contract or token pipeline without running a node.