Unified Confirmed Transaction

This event is triggered when:

A new transaction is mined.
A customer has a rule with the address variable type and the variable contains the address of the transaction as its value. Only the sender and recipient of the transaction are matched. However, for multitransfers, a specific trace (either sender or recipient) may be matched instead.

Schema

{
  "data": {
    "block_number": "integer",
    "block_hash": "string",
    "tx_id": "string",
    "tx_hash": "string",
    "timestamp": "integer",
    "status": "string",
    "transfers": ["array"],
    "multi_sig_transfers": ["array"],
    "fee": {}
  }
}

Field	Type	Description
`block_hash`	string	(Required) The block hash.
`block_number`	integer	(Required) The block number.
`timestamp`	integer	(Required) The UNIX timestamp when the block was mined/validated.
`tx_id`	string	(Required) The transaction identifier, such as the transaction hash or other unique identifier.
`tx_hash`	string	The transaction hash. This only applies to protocols where transactions have both an ID and a hash that might not always be the same value.
`status`	string	(Required) The transaction status when available. The default is `success` for successful transactions and `failed` for failed transactions.
`transfers`	array of transfers	An array of transfers that took place during the transaction. See the Transfer Schema below.
`multi_sig_transfers`	array of transfers	Applies to Dogecoin and Litecoin only. Contains transfers requiring multiple signatures. See the Multi Transfer Schema below.
`fee`	object	The fee paid for this transaction. The default shape is the native `Transfer`, but some protocols (e.g. Ethereum and other EVM chains) use the `EVMFee` shape instead.

This schema applies to the UNIFIED_V1 and UNIFIED_V1_RAW templates. ALL_DATA returns the chain's native transaction payload unmodified, with its own fields, shown below per protocol.

Examples

Base

MainnetSepolia

Base is an Ethereum L2 and is EVM-compatible. The native payload is a standard EVM transaction receipt with hex-encoded value/gas fields; the unified schema decodes these into a single native transfer and an EVMFee object.

{
  "chain_id": "eip155:8453",
  "protocol": "base",
  "network": "mainnet",
  "event_type": "unified_confirmed_tx",
  "data": {
    "block_number": 36783819,
    "block_hash": "0x8b7118b6627346a1636323836caae125afe6ddb78015fba17005e8e605516d46",
    "tx_id": "0x7561d91790acf0ea7c012dca189d4e2d26ac68e680ad49495ebfb5b796f6d567",
    "timestamp": 1760356985,
    "status": "success",
    "transfers": [
      {
        "asset": "native",
        "from": "0x8AE710c38CdAcb31cc7d821B65c8F58591345411",
        "to": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
        "value": 0
      }
    ],
    "fee": {
      "gas_used": 40247,
      "gas_price": 15924283,
      "gas_limit": 45600,
      "value": 640904617901,
      "max_fee_per_gas": 15948975,
      "max_priority_fee_per_gas": 800000
    }
  }
}

Sub-schemas

The transfers, multi_sig_transfers, and fee fields above follow one of the sub-schemas below, depending on protocol.

1. Transfer Schema

Represents an individual transfer of assets within transfers. Applies to:

base, bitcoin, bitcoincash, bnb, dogecoin, ethereum, kaia, litecoin, monad, polkadot, stellar, tron, xrp

Field	Type	Description
`asset`	string	The asset type of the transfer. For native tokens (e.g. ETH on Ethereum), `asset` is `native`. Non-native tokens use their own denomination.
`value`	integer	The value transferred, in the lowest denomination of the asset (e.g. wei for ETH, satoshi for BTC).
`from`	string	The sender's account address.
`to`	string	The recipient's account address.
`event_name`	string	A protocol-specific name for the transfer, if applicable — e.g. Bitcoin sets this to `vin` for inputs and `vout` for outputs.

📘
Info
On EVM chains, internal contract calls made during a transaction are represented separately using the Call Trace schema below, delivered via the unified_confirmed_tx_trace event rather than as transfers entries.

Call Trace Schema (EVM chains)

Represents the call tree of an EVM transaction, delivered via a separate unified_confirmed_tx_trace event.

{
  "data": {
    "calls": [
      {
        "type": "string",
        "from": "string",
        "to": "string",
        "value": "string",
        "gas": "string",
        "gas_used": "string",
        "input": "string"
      }
    ]
  }
}

Field	Type	Description
`type`	string	The type of call, indicating the kind of execution (e.g. `CALL`, `DELEGATECALL`).
`from`	string	The sender's account address.
`to`	string	The recipient's account address.
`value`	string	The value transferred, in the lowest denomination of the asset (in wei for EVM chains).
`gas`	string	The gas limit set for this call.
`gas_used`	string	The actual amount of gas used for the call.
`input`	string	The data sent with the call.
`output`	string	The data returned by the call, if any.

{
  "protocol": "ethereum",
  "network": "mainnet",
  "event_type": "unified_confirmed_tx_trace",
  "chain_id": "eip155:1",
  "data": {
    "type": "CALL",
    "from": "0xf52e602be034b221d5d56aa544f2df71d92fe77d",
    "to": "0x87870bca3f3fd6335c3f4ce8392d69350b4fa4e2",
    "value": "0x0",
    "gas": "0x26b14a",
    "gas_used": "0x1a0ef0",
    "input": "0x42b0b77c000000000000000000000000adc0a53095a0af87f3aa29fe0715b5c28016364e...",
    "calls": [
      {
        "type": "DELEGATECALL",
        "from": "0x87870bca3f3fd6335c3f4ce8392d69350b4fa4e2",
        "to": "0x5faab9e1adbddad0a08734be8a52185fd6558e14",
        "value": "0x0",
        "gas": "0x25553a",
        "gas_used": "0x1c7495",
        "calls": ["... nested calls omitted"]
      }
    ],
    "tx_id": "0x5eaaa56e1691f9d305343cfe3680c7705994ccb916c2666b1fab4cc560b22605",
    "tx_hash": "0x5eaaa56e1691f9d305343cfe3680c7705994ccb916c2666b1fab4cc560b22605",
    "timestamp": 1721827031,
    "block_hash": "0x570ba481efbfe549e7fad3965af2aa913131af8cabb5516e7c51110130cbbf60",
    "block_number": 20376644
  }
}

2. EVMFee Schema

Represents transaction fees on Ethereum and other EVM chains. Includes gas usage, price, and limits. Applies to:

base, bnb, ethereum, kaia, monad, optimism, polygon, tron

Field	Type	Description
`gas_used`	integer	The amount of gas used for the transaction.
`gas_price`	integer	The gas price.
`gas_limit`	integer	The gas limit.
`value`	integer	The fee value, in the lowest denomination of the asset (e.g. wei for ETH, sun for Tron).
`max_fee_per_gas`	integer	The maximum fee per gas set for this transaction.
`max_priority_fee_per_gas`	integer	The maximum priority fee per gas set for this transaction.

📘
Info
Tron's fee object extends EVMFee with additional bandwidth/energy fields: net_fee, net_usage, energy_fee, energy_usage, energy_usage_total, origin_energy_usage, and energy_penalty_total. See the Tron example in the picker above.

3. Multi Transfer Schema

Used for multi_sig_transfers, when a transaction involves multiple signatures. Applies to:

dogecoin, litecoin

Field	Type	Description
`asset`	string	The asset type of the transfer. For native tokens, `asset` is `native`. Non-native tokens use their own denomination.
`from`	array of strings	The senders' account addresses.
`value`	integer	The value transferred, in the lowest denomination of the asset.
`event_name`	string	A protocol-specific name for the transfer, if applicable.

Example

This example also applies to Litecoin (LTC).

{
  "event_type": "unified_confirmed_tx",
  "protocol": "dogecoin",
  "network": "mainnet",
  "chain_id": "bip122:1a91e3dace36e2be3bf030a65679fe82",
  "data": {
    "block_number": 5365974,
    "block_hash": "a5f8021d1a92710abab7c59b8346748843876abcb21366aac5245313b68f7920",
    "tx_id": "d7a5629397ab980b6c542ff6f3536cf72fdeb1551bab6952bc1a0399b22b37d9",
    "tx_hash": "d7a5629397ab980b6c542ff6f3536cf72fdeb1551bab6952bc1a0399b22b37d9",
    "timestamp": 1725553175,
    "status": "success",
    "transfers": [
      {
        "asset": "native",
        "from": "DHduiEL2zcf6Xi7QirCdwBnaZqapdMwugr",
        "value": 197459530046,
        "event_name": "vin"
      }
    ],
    "multi_sig_transfers": [
      {
        "asset": "native",
        "from": [
          "DU55Nw2hBbHsZHQAXa9jTR6p9c1YfPiYpC",
          "DGLjxM6RbGKLZzFhxo9Z6D4aSK5af4YnyX",
          "DCV1PZcx3KwCARYZUJUnvyz5SLbzAUeX7o"
        ],
        "value": 973612900000,
        "event_name": "vout"
      }
    ],
    "fee": {
      "asset": "native",
      "value": 27850
    }
  }
}

Schema

Examples

Base

Sub-schemas

1. Transfer Schema

Info

Call Trace Schema (EVM chains)

2. EVMFee Schema

Info

3. Multi Transfer Schema

Example

👋 Need Help?