AsyncAPI channel · Arbitrum · Arbitrum Public WebSocket APIs

eth_subscribe/newPendingTransactions

`eth_subscribe("newPendingTransactions")`. Accepted by Nitro for go-ethereum compatibility, but Arbitrum's centralized Sequencer orders transactions on receipt — there is no public mempool, so the stream is effectively empty / of limited use compared to L1 Ethereum.

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

Channel address

eth_subscribe/newPendingTransactions

Operations

publish
subscribeNewPendingTransactions
Open a `newPendingTransactions` subscription.
receiveNewPendingTransactions
Receive pending transaction hash notifications.

Messages

JsonRpcSubscribeRequestNewPendingTxs
eth_subscribe newPendingTransactions request
Content-Type: application/json
EthSubscriptionPendingTxHash
eth_subscription notification — pending tx hash
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.