Transaction status tracking

Track transaction confirmation events by hash or by sender address.

Choose A Topic

Need	Topic
Track one known transaction	`tx-status/{hash}`
Track transactions from one sender	`address/{bech32}`

Both topics deliver txStatus events. Address topics can also deliver accountDelta events.

{
  "action": "subscribe",
  "requestId": "tx-001",
  "topic": "tx-status/<hash>"
}

{
  "action": "subscribe",
  "requestId": "tx-001",
  "status": "ok",
  "topic": "tx-status/<hash>"
}

{
  "type": "txStatus",
  "data": {
    "hash": "a1b2c3...",
    "status": "success",
    "reason": null,
    "sender": "erd1..."
  }
}

Status	Meaning
`pending`	Seen but not finalized.
`success`	Finalized successfully.
`fail`	Finalized with failure; inspect `reason`.
`invalid`	Rejected as invalid.
`dropped`	Dropped before finalization.

Limit	Value
Active topics	64 per WebSocket connection
Delivery	After transaction status ingestion
Hash tracking	One topic per hash

{
  "action": "unsubscribe",
  "requestId": "tx-stop",
  "topic": "tx-status/<hash>"
}

After reconnect, resubscribe to still-pending hashes. For completed hashes, prefer a Gateway status lookup instead of keeping long-lived topics.