Products
Data Access Portal API SQD Network Supported Chains
Development SDK SQD Cloud SQD 360
Solutions
By Use Case DeFi & Trading Analytics AI Agents Wallets & Payments Compliance
By Industry Stablecoins RWA All Customers
Developers
Get Started Documentation Subsquid Subsquid Labs Dev Chat
Resources
Learn Blog Changelog
Company About Ecosystem Brand Assets
Customers Pricing
Talk to us
All chains
Flare

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
1
Data tables
3
Chain ID
14
Runtime
EVM
Coverage
Real-time + archive
Start block
0 (genesis)
License
Open-source SDK

Networks

flare-mainnet
Real-time EVM mainnet 3 tables

Flare on SQD

Validated at ingestion

Flare 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

3 Flare tables (blocks, transactions & logs), 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 Flare 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 Flare indexer on your own infrastructure or on SQD Cloud.

Build with Flare data

Common production patterns teams build 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.

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.

Stream Flare data in two lines

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

1curl --compressed -X POST \
2 'https://portal.sqd.dev/datasets/flare-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 }'
flare-mainnet/stream
EVM · blocks 0–100

Frequently asked questions

How does SQD compare to running a Flare RPC node?
A Flare RPC node serves raw bytes for recent state and rate-limits per request. SQD's Portal pre-indexes the full Flare archive into decoded, schema-typed tables (blocks, transactions & logs) 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 Flare data?
The public Portal endpoint at portal.sqd.dev/datasets/flare-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 Flare 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 Flare 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 Flare explorer, the SQD Portal is what you would back it with.
Can I self-host SQD's Flare indexer?
Yes. Both the Squid SDK and the Pipes SDK are open-source. You can run a Flare 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 Flare data to a data warehouse or pipeline?
Yes. The Pipes SDK streams Flare 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 Flare data?
Every Flare 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 Flare data?
Yes. Flare 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

0g Testnet ADI Chain Alpen Testnet Arbitrum Blueberry Arthera Avalanche B3 Beam

Start building with Flare

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

Try the Portal Read Docs