OP

EVM Layer 2 / Chain ID 10

Optimism is an Ethereum Layer 2 using optimistic rollups, powering a superchain ecosystem of fast and affordable blockchain applications.

Website Explorer

Quick Facts

Networks 2

Runtime EVM

Chain ID 10

Real-time Yes

Data tables 5

Category Layer 2

Networks: 2
Data tables: 5
Chain ID: 10
Runtime: EVM
Coverage: Real-time + archive
Start block: 0 (genesis)
License: Open-source SDK

Networks

optimism-mainnet

Real-time EVM mainnet 5 tables

optimism-sepolia

EVM testnet 3 tables

OP on SQD

Validated at ingestion

OP data is validated by SQD Network workers before it reaches the Portal. Validation is performed across the network rather than by a single ingestion node, so a faulty upstream source can't poison the dataset.

Decoded, schema-typed

5 OP tables (blocks, transactions, logs & traces), decoded and schema-typed, ready to query. Your indexer queries the data directly without writing RLP parsers.

Archive plus real-time

Single Portal endpoint serves OP from genesis through the current head, with sub-second hot-path latency. No separate streaming pipeline to wire up.

Open-source SDK

Both the Squid SDK and the Pipes SDK are open-source. Connectors for Postgres, ClickHouse, MongoDB, SQLite and Parquet, plus a custom-target hook. Run your OP indexer on your own infrastructure or on SQD Cloud.

Build with OP data

Common production patterns teams build with SQD on OP.

DeFi & Trading

Index swaps, liquidations, and positions on OP in real time.

Analytics

Build dashboards and metrics from full OP historical state.

AI Agents

Give agents structured, decoded OP data with the MCP server.

Wallets & Payments

Power balance, transfer, and history views for OP wallets.

Compliance & KYT

Validated OP data for transaction monitoring and audits.

Stablecoins

Track every mint, burn, and transfer of OP stablecoins.

Real-World Assets

Auditable OP data for tokenized RWA issuance and transfers.

Available Data

blocks

Block headers with timestamps, gas usage, miner info, and consensus data.

transactions

All onchain transactions with sender, receiver, value, gas, and input data.

logs

Event logs emitted by smart contracts, the primary source for tracking DeFi, NFT, and token activity.

traces

Internal transactions and call traces showing the full execution path of each transaction.

state_diffs

State changes per transaction, storage slot modifications, balance changes, and nonce updates.

Stream OP data in two lines

Example below uses the public OP endpoint, no API key required for development. For full SDK reference, see the documentation.

1curl --compressed -X POST \
'https://portal.sqd.dev/datasets/optimism-mainnet/stream' \
-H 'Content-Type: application/json' \
-d '{
    "type": "evm",
    "fromBlock": 0,
    "toBlock": 100,
    "fields": {
      "block": {"number":true,"timestamp":true},
      "transaction": {
        "hash": true,
        "from": true,
        "to": true,
        "value": true
      }
    },
    "transactions": [{}]
  }'

optimism-mainnet/stream

EVM · blocks 0–100

Frequently asked questions

How does SQD compare to running an OP RPC node?

An OP RPC node serves raw bytes for recent state and rate-limits per request. SQD's Portal pre-indexes the full OP archive into decoded, schema-typed tables (blocks, transactions, logs & traces) and serves them as a single streaming endpoint. You skip the multi-day node sync, archive storage, monitoring, and scale-out work, and pay only for the data you stream.

What does SQD cost for OP data?

The public Portal endpoint at portal.sqd.dev/datasets/optimism-mainnet is free for development with no API key. Production workloads run on the SQD Portal with tiered pricing based on the network and request volume. See the pricing page for current tiers, or contact us for an enterprise quote.

How is SQD's OP data different from a block explorer like Etherscan?

Block explorers are read-optimized for human browsing of single blocks or addresses. SQD is built for programmatic indexing: stream millions of OP blocks into your own database, run analytical queries across the full history, and back production applications with decoded data. Output is structured tables, not HTML pages, and there are no per-call rate limits geared toward UI traffic. If you wanted to build your own OP explorer, the SQD Portal is what you would back it with.

Can I self-host SQD's OP indexer?

Yes. Both the Squid SDK and the Pipes SDK are open-source. You can run an OP indexer on your own infrastructure pointing at the SQD Network or the Portal. SQD Cloud also offers managed hosting if you'd rather not operate it yourself.

Can I export OP data to a data warehouse or pipeline?

Yes. The Pipes SDK streams OP data from the Portal into Postgres, ClickHouse, MongoDB, SQLite, Parquet, or a custom target you implement. See the SDK docs for the connector reference.

Does SQD validate OP data?

Every OP block ingested into SQD is validated by the SQD Network workers (hash chain, parent reference, and where applicable finality) before it reaches the Portal. Validation is performed across the network, not by a single ingestion process, so a faulty upstream node can't poison the dataset.

Does SQD support real-time OP data?

Yes. OP is served with both real-time and historical data from the same Portal endpoint, with sub-second latency on the hot path. No separate streaming pipeline to wire up.

See other chains supported by SQD

Start building with OP

Access OP data through the SQD Portal, free tier available.

Try the Portal Read Docs