Flare

EVM Layer 1 / Chain ID 14

Flare is an EVM-compatible Layer 1 blockchain designed to provide decentralized data access for building cross-chain applications.

Website Explorer

Quick Facts

Networks 1

Runtime EVM

Chain ID 14

Real-time Yes

Data tables 3

Category Layer 1

Networks

flare-mainnet

Real-time EVM mainnet 3 tables

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.

How to index Flare blockchain data

Stream Flare event logs, transactions, and blocks from the SQD Portal in two lines of code. The example below uses the public endpoint, no API key required for development.

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

flare-mainnet/stream

EVM · blocks 0–100

Build with Flare data

Common production patterns teams ship with SQD on Flare.

DeFi & Trading

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

Analytics

Build dashboards and metrics from full Flare historical state.

AI Agents

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

Wallets & Payments

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

Compliance & KYT

Validated Flare data for transaction monitoring and audits.

Stablecoins

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

Real-World Assets

Auditable Flare data for tokenized RWA issuance and transfers.

Frequently asked questions

How do I index Flare blockchain data?

Use the SQD Portal API at portal.sqd.dev/datasets/flare-mainnet or the open-source Squid SDK. Both stream Flare blocks, transactions, and event logs in real time. The free tier supports development; paid Portal deployments cover production workloads with SLA-backed latency.

Is the Flare API free?

Yes. SQD provides a free public Portal endpoint for Flare with no API key required. For higher rate limits, dedicated infrastructure, and SLA-backed uptime, see the SQD Pricing page.

What Flare data tables does SQD provide?

SQD indexes 3 data tables for Flare: blocks, transactions, logs. Each table is decoded, validated at ingestion, and queryable through the Portal API.

Does SQD support real-time Flare data?

Yes. SQD provides sub-second latency on Flare mainnet through the Portal's hot path. Both real-time streaming and full historical access are available from the same API.

What's the difference between SQD and an RPC node for Flare?

An RPC node serves raw, unvalidated Flare data limited to recent state. SQD's Portal indexes the full Flare history, decodes it into queryable tables, validates every block at ingestion, and serves it through a typed SDK, no node operations required.

Can I self-host Flare indexing with SQD?

Yes, the Squid SDK is open-source under the GPLv3 license. You can run your own indexer against the SQD Network or the Portal, or deploy on SQD Cloud for fully managed hosting.