Blast

EVM Layer 2 / Chain ID 81457

Blast is an Ethereum Layer 2 with native yield for ETH and stablecoins, offering auto-compounding returns for users and protocols.

Website Explorer

Quick Facts

Networks 2

Runtime EVM

Chain ID 81457

Real-time No

Data tables 5

Category Layer 2

Networks: 2
Data tables: 5
Chain ID: 81457
Runtime: EVM
Coverage: Archive
Start block: 0 (genesis)
License: Open-source SDK

Networks

blast-l2-mainnet

EVM mainnet 5 tables

blast-sepolia

EVM testnet 3 tables

Blast on SQD

Validated at ingestion

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

Build with Blast data

Common production patterns teams build with SQD on Blast.

DeFi & Trading

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

Analytics

Build dashboards and metrics from full Blast historical state.

AI Agents

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

Wallets & Payments

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

Compliance & KYT

Validated Blast data for transaction monitoring and audits.

Stablecoins

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

Real-World Assets

Auditable Blast data for tokenized RWA issuance and transfers.

Teams using SQD on Blast

Production case studies from a team indexing Blast with SQD.

Social Gaming

Fantasy.Top

Real-time leaderboards and reward tracking on Blast

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

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

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

blast-l2-mainnet/stream

EVM · blocks 0–100

Frequently asked questions

How does SQD compare to running a Blast RPC node?

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

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

Can I self-host SQD's Blast indexer?

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

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

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

Blast historical data is available through the Portal archive. Real-time streaming for Blast is on the roadmap, contact us to flag your use case for prioritization.

See other chains supported by SQD

Start building with Blast

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

Try the Portal Read Docs