BNB Chain

EVM Layer 1 / Chain ID 56

BNB Smart Chain (formerly BSC) is a high-throughput EVM-compatible blockchain operated by Binance, supporting a large ecosystem of DeFi and gaming dApps.

Website Explorer

Quick Facts

Networks 4

Runtime EVM

Chain ID 56

Real-time Yes

Data tables 5

Category Layer 1

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

Networks

binance-mainnet

Real-time EVM mainnet 5 tables

opbnb-mainnet

EVM mainnet 3 tables

binance-testnet

EVM testnet 3 tables

opbnb-testnet

EVM testnet 3 tables

BNB Chain on SQD

Validated at ingestion

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

Build with BNB Chain data

Common production patterns teams build with SQD on BNB Chain.

DeFi & Trading

Index swaps, liquidations, and positions on BNB Chain in real time.

Analytics

Build dashboards and metrics from full BNB Chain historical state.

AI Agents

Give agents structured, decoded BNB Chain data with the MCP server.

Wallets & Payments

Power balance, transfer, and history views for BNB Chain wallets.

Compliance & KYT

Validated BNB Chain data for transaction monitoring and audits.

Stablecoins

Track every mint, burn, and transfer of BNB Chain stablecoins.

Real-World Assets

Auditable BNB Chain data for tokenized RWA issuance and transfers.

Teams using SQD on BNB Chain

Production case studies from teams indexing BNB Chain with SQD.

Privacy Infrastructure

RAILGUN

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

DeFi

PancakeSwap

Multi-chain DEX data indexing at scale

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

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

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

binance-mainnet/stream

EVM · blocks 0–100

Frequently asked questions

How does SQD compare to running a BNB Chain RPC node?

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

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

Can I self-host SQD's BNB Chain indexer?

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

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

Every BNB Chain 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 BNB Chain data?

Yes. BNB Chain 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.