MegaETH Data: Index Real-Time EVM Activity

Index MegaETH's 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.

MegaETH calls itself the first real-time blockchain, an Ethereum Layer 2 that settles on Ethereum while pushing execution to hardware limits. Instead of batching transactions into slow blocks, a single high-powered sequencer streams them through a specialized pipeline and emits mini-blocks on a millisecond cadence, with the network targeting throughput north of 100,000 transactions per second. Because it stays EVM-compatible, Solidity contracts, EVM addresses, and existing tooling deploy unchanged, and gas is paid in ETH. To your code MegaETH reads like Ethereum; to your infrastructure it moves far faster. The team frames it at megaeth.com.

That speed is exactly where the data problem starts. A chain that produces blocks every few milliseconds and aims for six-figure TPS emits logs, traces, and decoded calls faster than any polling loop can keep pace with. An indexer that samples the RPC on a timer, or that falls even slightly behind the head, never catches up: the tip keeps moving while you page through history. Indexing Co covers MegaETH 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 MegaETH L2 blocks

Ingest blocks, logs, traces

Decode ABIs to events

Transform your JavaScript

Deliver your database

Why MegaETH data is hard

Millisecond Blocks Outrun Polling MegaETH's sequencer emits mini-blocks on a roughly 10-millisecond cadence, hundreds of times faster than the block time an eth_getLogs polling loop was built for. Sample on a timer and you either miss ranges between polls or hammer the endpoint into rate limits. A live feed has to consume the stream at head speed, not sip from it on an interval.

Real-Time or You Fall Behind Forever At six-figure TPS the chain head moves faster than a lagging consumer can backfill. Slip behind by even a few seconds and you are paging through a widening gap while new mini-blocks keep landing on top. Staying pinned to the tip is not a nice-to-have on MegaETH; it is the only way an indexer ever converges.

Streaming EVM and State Deltas MegaETH streams transactions continuously and ships state deltas rather than full histories between its sequencer, full, and replica nodes. Your dataset still needs strict per-block, per-log ordering and deterministic indices, so the indexer has to reconstruct a clean, linear, reorg-safe history from a firehose that was engineered for throughput, not for tidy replay.

Your Own DB, Not a Hosted API A single-sequencer, data-center-grade chain is not something you point a generic hosted query API at and hope it keeps up. Powering an app or analytics workload on MegaETH means owning the decoded data in your own store, shaped the way your product queries it, instead of renting someone else's rate-limited schema.

What Indexing Co delivers for MegaETH

The DIY Path

Stand up and maintain the whole stack yourself.

Run a MegaETH node or wire up a third-party RPC.
Consume mini-blocks at head speed instead of polling on a timer.
Reconstruct strict ordering from a continuous streaming feed.
Build volume backfill, reorg handling, and real-time delivery from scratch.

Indexing Co

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

MegaETH 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 MegaETH, for example
Contract events and logs	DEX swaps, perp fills, lending borrows and liquidations
Token transfers (ERC-20, ERC-721)	Stablecoin payments, wstETH movements, NFT mints
Decoded transactions and traces	Smart-wallet user operations, contract deployments
Protocol and account state	Pool reserves, perp positions, account 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;
}

MegaETH with Indexing Co

Run it yourself if

You want full control of node infrastructure and have the team to consume MegaETH's mini-block stream at head speed, reconstruct ordering, and build backfill and reorg handling in-house.

Use Indexing Co if

You want MegaETH 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 MegaETH node?

No. Indexing Co sources MegaETH blocks, logs, and traces for you, including full historical data, so you never operate a node or poll a rate-limited RPC endpoint.

How does Indexing Co keep up with MegaETH's millisecond blocks?

The pipeline consumes the chain at head speed rather than sampling the RPC on a timer, so it stays pinned to the tip as mini-blocks land. That is what keeps a live feed from falling behind a chain designed for real-time throughput.

Can I index any protocol on MegaETH?

Yes. Point a pipeline at any MegaETH contract or set of contracts, from DEXes and perp venues to your own deployments, and we decode the events against the right ABI. Because MegaETH is EVM-compatible, standard Solidity ABIs apply.

Where does the MegaETH data go?

Into your own destination: PostgreSQL, BigQuery, a warehouse, or a webhook. You define the output schema and own the storage.

Can I get complete historical MegaETH data?

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

Get Started

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