FIREHOSE / BLOCKCHAIN DATA STREAMING

Every block.
Your level of detail.

Stream the full execution picture, or focus on the contracts that matter. One gRPC stream from historical blocks to the live chain head.

Try Firehose Explore pricing

Live + historical Extended EVM data Server-side filtering

ONE STREAM, TWO WAYS TO BUILD

Choose how much of the chain you need.

Full blocks

Every transaction, log and execution detail.

Filtered blocks

Matching transactions, with their logs and execution context.

Chain

Filter

1 hour of streamingV2 / V3 / V4 · any contract

Full blocks5.83 GB

Filtered blocks1.97 GB

66.3% less data

Try this filter

FROM INDEXING TO LIVE MONITORING

Build with execution data.

Index the whole picture

Feed graph-node or your own pipeline with ordered blocks. Use extended data where available for calls, balances and storage changes.

Full-block streaming

Follow a protocol

Watch a set of token or trading contracts. Filter by log emitter and event signature, then process the matching transactions in your application.

Contract-filtered streaming

Replay, then stay live

Start at a historical block or resume from a cursor. Follow new blocks and handle undo messages when the chain reorganizes.

One streaming interface

READY TO TRY

Start with a stream you know.

Open an example in the App. The network, contracts and event filters are ready to use.

Ethereum

Robinhood’s Transfer signature also matches ERC-721. Select token contracts or classify logs in your client.

IN PRACTICE / ROBINHOOD CHAIN

A focused stream for a fast-moving chain.

We compared full and contract-filtered Firehose data for USDG on Robinhood mainnet. In block 63,061,820, filtering kept all 37 USDG logs across 8 matching transactions, down from 21 total transactions.

The matching transactions keep their execution context. Data savings depend on contract activity and transaction size. The hourly comparison above measures uncompressed payloads, the basis for Firehose billing.

0x5fc5360d0400a0fd4f2af552add042d716f1d168

Open the USDG example Read the comparison

Documentation

StreamingFast

Firehose documentation

Explore the architecture, components and setup guides behind Firehose.

The Graph

Firehose for indexers

Learn how Firehose fits into The Graph’s blockchain indexing stack.

Know what reaches your app.

Does filtering return only my selected logs?

It retains whole transactions that contain matching logs. Other logs in those transactions can still appear, so select the desired receipt logs in your client. With all block headers enabled, blocks without matches still let you track progress.

Can I match logs from internal contract calls?

Yes. Log filters match the emitting contract, including logs emitted during internal calls. The emitter is not necessarily the top-level transaction destination, and it is not the wallet sending or receiving a token.

Are all Firehose endpoints extended?

No. Available fields depend on the chain and block model. Extended EVM endpoints add execution traces and state changes; base EVM endpoints carry a smaller model. Check the selected network in the App before building around extended fields.

When should I use Substreams or WebSockets?

Use Firehose for block and transaction context. Substreams can run custom transformations and emit narrower application data. Pinax WebSockets offer decoded event streams with their own filtering interface. Compare the same events when measuring delivery latency.

Your next stream starts here.

Select a network, choose full blocks or contract filters, and inspect real responses in the App.

Open Firehose Try it Browse supported chains