Sei Data: Index Trades, Tokens, and Contracts on the Sei EVM

Index Sei's parallelized EVM contract events, token transfers, and decoded trades in one pipeline, delivered to your own database. Real-time and full historical data, no node to run.

Sei calls itself the blockchain for trading, a Layer 1 built for the performance digital asset markets demand. Its parallelized EVM, shipped with Sei V2, runs Solidity contracts with full bytecode compatibility while executing independent transactions side by side instead of one at a time. Twin-Turbo consensus drives roughly 400ms block times and near-instant finality, which is why exchanges, perps venues, and high-frequency DeFi land here. Sei now runs as an EVM-only chain after its SIP-3 transition retired the Cosmos side, including CosmWasm and IBC. You can read how the team frames it at sei.io.

That speed is the data problem. When trades settle in under half a second and parallel execution packs orders into every block, swap events, order updates, and token transfers stream off Sei faster than a hand-rolled scraper can keep up. Indexing Co covers the Sei EVM 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 Sei EVM blocks

Ingest blocks, logs, traces

Decode ABIs to events

Transform your JavaScript

Deliver your database

Why Sei data is hard

Trading-Grade Throughput Sei's parallelized EVM is tuned for trading volume, processing independent transactions concurrently to clear far more orders per block than a single-threaded chain. Capturing that flow of swaps, fills, and transfers in real time, without lagging the chain head, is a standing engineering load most teams underestimate.

Sub-Second Finality, In Order With roughly 400ms block times under Twin-Turbo consensus, blocks land several times a second and a real-time consumer has almost no slack to fall behind. An indexer has to ingest, decode, and deliver at that cadence while preserving exact transaction order, which matters for price feeds, PnL, and any trade-sensitive dataset.

Decoding the Sei EVM A useful Sei dataset spans many contracts at once: DEX pools, perps and orderbook venues, lending markets, and the tokens moving across them. Each needs its own ABI, and proxy upgrades keep moving the right ABI target, so raw logs are useless until they are decoded against the correct interface.

Your Own DB, Not a Hosted API Public RPC endpoints and rented query APIs leave you rate-limited and stuck inside someone else's schema. Running a trading app or analytics workload on Sei means owning the data in your own store, indexed and shaped the exact way your product reads it.

What Indexing Co delivers for Sei

The DIY Path

Stand up and maintain the whole stack yourself.

Run a Sei archive node or wire up a third-party EVM 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 Sei to your store.

Sei EVM 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 Sei, for example
Contract events and logs	DEX swaps, perps order and fill events
Token transfers (ERC-20, ERC-721)	Stablecoin payments, NFT mints
Decoded transactions and traces	Smart-wallet and router multicalls
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;
}

Sei with Indexing Co

Run it yourself if

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

Use Indexing Co if

You want Sei EVM contract events, token transfers, and decoded trades 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 Sei node?

No. Indexing Co sources Sei EVM 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 the Sei EVM?

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

Does Indexing Co keep up with Sei's sub-second blocks?

Yes. The pipeline ingests Sei's roughly 400ms blocks in real time and preserves transaction order, so trade-sensitive data stays correct as the chain advances.

Where does the Sei 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 Sei data?

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

Get Started

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