Arbitrum

EVM Layer 2 / Chain ID 42161

Arbitrum is an Ethereum Layer 2 scaling solution using optimistic rollups to deliver high throughput and low-cost transactions while inheriting Ethereum security.

Website Explorer

Quick Facts

Networks 3

Runtime EVM

Chain ID 42161

Real-time Yes

Data tables 4

Category Layer 2

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

Networks

arbitrum-one

Real-time EVM mainnet 4 tables

arbitrum-nova

EVM mainnet 4 tables

arbitrum-sepolia

Real-time EVM testnet 3 tables

Arbitrum on SQD

Validated at ingestion

Arbitrum 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

4 Arbitrum 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 Arbitrum 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 Arbitrum indexer on your own infrastructure or on SQD Cloud.

Build with Arbitrum data

Common production patterns teams build with SQD on Arbitrum.

DeFi & Trading

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

Analytics

Build dashboards and metrics from full Arbitrum historical state.

AI Agents

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

Wallets & Payments

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

Compliance & KYT

Validated Arbitrum data for transaction monitoring and audits.

Stablecoins

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

Real-World Assets

Auditable Arbitrum data for tokenized RWA issuance and transfers.

Teams using SQD on Arbitrum

Production case studies from teams indexing Arbitrum with SQD.

Perpetual DEX

GMX

Enhanced query performance, simplified cross-chain scaling

Privacy Infrastructure

RAILGUN

Expanded privacy pools from single-chain to multi-chain with reduced balance scanning times

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.

Stream Arbitrum data in two lines

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

1curl --compressed -X POST \
'https://portal.sqd.dev/datasets/arbitrum-one/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": [{}]
  }'

arbitrum-one/stream

EVM · blocks 0–100

Frequently asked questions

How does SQD compare to running an Arbitrum RPC node?

An Arbitrum RPC node serves raw bytes for recent state and rate-limits per request. SQD's Portal pre-indexes the full Arbitrum 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 Arbitrum data?

The public Portal endpoint at portal.sqd.dev/datasets/arbitrum-one 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 Arbitrum 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 Arbitrum 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 Arbitrum explorer, the SQD Portal is what you would back it with.

Can I self-host SQD's Arbitrum indexer?

Yes. Both the Squid SDK and the Pipes SDK are open-source. You can run an Arbitrum 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 Arbitrum data to a data warehouse or pipeline?

Yes. The Pipes SDK streams Arbitrum 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 Arbitrum data?

Every Arbitrum 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 Arbitrum data?

Yes. Arbitrum 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 Arbitrum

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

Try the Portal Read Docs