AsyncAPI channel · Optimism · Optimism (OP Stack) WebSocket JSON-RPC API

eth_subscribe.newPendingTransactions

Subscription that pushes the hash of every new transaction that enters the mempool. By default only transaction hashes are streamed; passing `true` as the second parameter requests the full transaction object (op-geth honours the same flag as upstream geth).

Provider: Optimism AsyncAPI: v2.6.0 Spec: Optimism (OP Stack) WebSocket JSON-RPC API Operations: 2 Messages: 3

Channel address

eth_subscribe.newPendingTransactions

Operations

publish
subscribeNewPendingTransactions
Subscribe to pending-transaction notifications.
onPendingTransaction
Receive a notification for each new pending transaction.

Messages

SubscribeNewPendingTxRequest
JSON-RPC request to subscribe to pending transactions.
Content-Type: application/json
SubscribeResponse
JSON-RPC response containing the subscription id.
Content-Type: application/json
PendingTxNotification
Notification carrying a pending transaction hash (or full tx).
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.