All chains
Scroll

Scroll

EVM Layer 2 / Chain ID 534352

Scroll is a zkEVM-based Ethereum Layer 2 that provides native compatibility for existing Ethereum applications and tools.

Quick Facts
Networks 2
Runtime EVM
Chain ID 534352
Real-time No
Data tables 4
Category Layer 2
Networks
2
Data tables
4
Chain ID
534352
Runtime
EVM
Coverage
Archive
Start block
0 (genesis)
License
Open-source SDK

Networks

scroll-mainnet
EVM mainnet 4 tables
scroll-sepolia
EVM testnet 4 tables

Scroll on SQD

Validated at ingestion

Scroll 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 Scroll tables (blocks, transactions, logs & traces), decoded and schema-typed, ready to query. Your indexer queries the data directly without writing RLP parsers.

Full historical archive

SQD's Scroll archive covers historical state in one endpoint. Real-time on the roadmap.

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

Build with Scroll data

Common production patterns teams build with SQD on Scroll.

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 Scroll data in two lines

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

1curl --compressed -X POST \
2 'https://portal.sqd.dev/datasets/scroll-mainnet/stream' \
3 -H 'Content-Type: application/json' \
4 -d '{
5 "type": "evm",
6 "fromBlock": 0,
7 "toBlock": 100,
8 "fields": {
9 "block": {"number":true,"timestamp":true},
10 "transaction": {
11 "hash": true,
12 "from": true,
13 "to": true,
14 "value": true
15 }
16 },
17 "transactions": [{}]
18 }'
scroll-mainnet/stream
EVM · blocks 0100

Frequently asked questions

How does SQD compare to running a Scroll RPC node?
A Scroll RPC node serves raw bytes for recent state and rate-limits per request. SQD's Portal pre-indexes the full Scroll 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 Scroll data?
The public Portal endpoint at portal.sqd.dev/datasets/scroll-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 Scroll 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 Scroll 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 Scroll explorer, the SQD Portal is what you would back it with.
Can I self-host SQD's Scroll indexer?
Yes. Both the Squid SDK and the Pipes SDK are open-source. You can run a Scroll 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 Scroll data to a data warehouse or pipeline?
Yes. The Pipes SDK streams Scroll 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 Scroll data?
Every Scroll 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 Scroll data?
Scroll historical data is available through the Portal archive. Real-time streaming for Scroll is on the roadmap, contact us to flag your use case for prioritization.

See other chains supported by SQD

Start building with Scroll

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