AsyncAPI channel · Chainstack · Chainstack RPC WebSocket APIs

monad/eth_subscribe/monadNewHeads

Subscribe to Monad block headers via the consensus lifecycle. Each notification includes a `blockId` and `commitState` (Proposed / Voted / Finalized / Verified). The same block number may appear multiple times as its `commitState` advances. Typically delivers roughly one second ahead of the standard `newHeads` event.

Open source AsyncAPI → All Chainstack channels Chainstack provider profile
Provider: Chainstack AsyncAPI: v2.6.0 Spec: Chainstack RPC WebSocket APIs Operations: 2 Messages: 2

Channel address

monad/eth_subscribe/monadNewHeads

Operations

publish
monadSubscribeMonadNewHeads
Subscribe to monadNewHeads on Monad
monadMonadNewHeadsNotification
Receive Monad monadNewHeads notifications

Messages

monadSubscribeMonadNewHeads
Subscribe to Monad block headers across the consensus lifecycle.
Content-Type: application/json
monadSubscriptionMonadNewHeads
Push notification carrying a Monad block header tagged with its commitState.
Content-Type: application/json

About AsyncAPI

The AsyncAPI specification describes event-driven APIs the way OpenAPI describes request/response APIs. A channel is the named pipe — a webhook URL, a Kafka topic, a WebSocket route, an MQTT subject — that producers and consumers publish or subscribe to. Each channel carries one or more messages with structured payloads, and an operation declares whether a given party sends or receives on that channel.

Browse every event-driven channel on the APIs.io network or compare with the broader Naftiko capability, Agent Skill, and MCP server surfaces of the same providers.