Real-time blockchain data, pushed to your stack.

Real-time blockchain data is onchain activity delivered the moment it happens, not on a polling delay. Quicknode ships it three ways: Webhooks for event notifications, Streams for push-based data pipelines, and Solana gRPC, Blazar WSS, and HyperCore gRPC for raw low-latency access. Pick the product that matches your workload.

Use Webhooks when you want filtered event notifications with no infrastructure to run: pick a no-code template, add your wallet or contract address and endpoint, and start receiving events. Use Streams when you need ordered data pushed to a destination like a webhook, data warehouse, or analytics system, with backfills to replay history. Use Solana gRPC, Blazar WSS, or HyperCore gRPC when you need the lowest latency and direct protocol access for trading, arbitrage, MEV, and monitoring.

Webhooks and Streams run across most of the chains Quicknode supports. The raw protocol feeds are chain-specific: Solana gRPC and Blazar WSS cover Solana, and HyperCore gRPC covers Hyperliquid, including gRPC-exclusive L2 and L4 order book depth. Check the docs for the current per-product chain list.

Both Webhooks and Streams use usage-based pricing, metered by API credits. Webhooks charge per matching block, so you pay only when an event matches your filter and delivers. Streams meter by the number of blocks your stream processes, so spend tracks usage and stays easy to forecast. On the raw feeds, Blazar WSS is included free on every plan, Solana gRPC is available on Scale and Business plans, and HyperCore gRPC is included on all paid plans. Solana and HyperCore WSS and gRPC meter usage in API credits based on the volume of data delivered through the subscription. See pricing for the full breakdown.

Blazar WSS is included free on every plan, and HyperCore gRPC is included on all paid plans. Solana gRPC is available on Scale and Business plans. Solana and HyperCore WSS and gRPC meter usage in API credits based on the volume of data delivered through the subscription. No separate contract is required to start.

Yes. They share one account and one API key. A common setup pairs Webhooks for alerting, Streams for warehousing, and a gRPC feed for the latency-sensitive path, all under the same billing and dashboard.

Running your own pipeline means your team spends time and effort operating nodes, handling reorgs, backfilling history, and keeping delivery ordered and reliable. With Streams, Quicknode handles the heavy lifting -reorg logic, guaranteed exactly-once delivery, automatic retries, replay through backfills, and server-side filtering - so your team can focus on building your product instead of maintaining infrastructure.