get_transaction_lifecycle

Retrieve a “transaction_lifecycle” (when “fetch” is true) and follow its life-cycle (with “listen” is true)

Usage

When following a transaction, any new block referencing that transaction will trigger an updated version of “transaction_lifecycle” to be sent. When one of those blocks passes irreversibility, you will also receive an updated transaction_lifecycle object.

Example request:

{
  "type": "get_transaction",
  "fetch": true,
  "listen": true,
  "data": {
    "id": "da1abcf7e205cf410c35ba3d474fd8d854a7513d439f7f1188d186493253ed24"
  }
}

Arguments

id required string
The transaction ID you want to keep track of

Responses

On both fetch: true and listen: true requests, dfuse will stream back TransactionLifecycle objects.