Transaction history — history

Subscribe to the history channel to follow an address's transaction activity. By default you receive confirmed history entries; add pending: true to receive the address's pending (mempool) transactions instead.

{ "action": "subscribe", "channel": "history", "address": "0xa1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6e7f8a9b0" }
{ "action": "subscribe", "channel": "history", "address": "0xa1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6e7f8a9b0", "pending": true }

history — confirmed

One event per new confirmed history entry. A single block may produce several for the same address (one per transaction the address appears in).

{
  "type": "history",
  "data": {
    "address": "0xa1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6e7f8a9b0",
    "height": 19234567,
    "block_n": 42
  }
}

Field	Type	Description
type	string	Always "history".
data.address	string	The subscribed address.
data.height	integer	Block height where the appearance happened.
data.block_n	integer	Position of the transaction within the block.

pending — pending (pending: true)

One event per pending (unconfirmed) transaction that touches the address. The data payload is the pending-transaction shape documented on the All pending transactions page, plus the matched address.

{
  "type": "pending",
  "address": "0xa1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6e7f8a9b0",
  "data": { "hash": "0x...", "from": "0x...", "to": "0x...", "value": "1000000000000000000", "input": "0x" }
}

Field	Type	Description
type	string	Always "pending".
address	string	The subscribed address the transaction touched.
data	object	The pending-transaction payload — see All pending transactions.

Optional feature

Pending events are an optional feature and may not be available on every network. Subscribing where pending tracking is unavailable succeeds, but no pending events arrive.