Codestin Search App

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": {}
  }
}

The table below shows the schema breakdown:

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 Bitcoin, where transactions have 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 took place during the transaction.
`multi_sig_transfers`	array of transfers	Applies to DOGE and LTC only. Contains transfers requiring multiple signatures.
`fee`	object	The fee paid for this transaction. The default value is `Transfer` but some protocols like Ethereum use their object to represent the fee.

1. Transfer Schema

Represents transfers of assets.

bitcoin/mainnet
bitcoin/testnet
bitcoincash/mainnet
bitcoincash/testnet
bnb/mainnet
bnb/testnet
dogecoin/testnet
ethereum/mainnet
kaia/mainnet
kaia/testnet
litecoin/testnet
monad/mainnet
monad/testnet
polkadot/mainnet
polkadot/westend
stellar/mainnet
stellar/testnet
tron/mainnet
tron/nile
xrp/mainnet
xrp/testnet

The table below shows the schema breakdown:

Field	Type	Description
asset	string	The asset type of the balance. For native tokens like Ethereum, the asset will be set to "native". For non-native tokens will have their denomination.
value	integer	The value transferred. The value is in the lowest denomination of the asset. For example: For ETH, the value is in `wei`. For BTC, the value is in `satoshi`.
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). This field can provide more information on the type of transfer.

For example, Bitcoin will set this to vin for inputs and vout for outputs.

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

The table below shows the schema breakdown:

Field	Type	Description
type	string	The type of call indicates 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. The value is in the lowest denomination of the asset. For ETH, the value is in wei.
gas	string	The gas limit set for this call,
gas_used	string	The actual amount of gas used for the transaction.
input	string	The data sent with the call.
output	string	The data returned by the call, if any.

Example

{
   "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":"0x42b0b77c000000000000000000000000adc0a53095a0af87f3aa29fe0715b5c28016364e000000000000000000000000",
      "calls":[
         {
            "type":"DELEGATECALL",
            "from":"0x87870bca3f3fd6335c3f4ce8392d69350b4fa4e2",
            "to":"0x5faab9e1adbddad0a08734be8a52185fd6558e14",
            "value":"0x0",
            "gas":"0x25553a",
            "gas_used":"0x1c7495",
            "input":"0x42b0b77c000000000000000000000000adc0a53095a0af87f3aa29fe0715b5c28016364e000000000000000000000000",
            "calls":[
               {
                  "type":"DELEGATECALL",
                  "from":"0x87870bca3f3fd6335c3f4ce8392d69350b4fa4e2",
                  "to":"0x0063bcd116694c21f6a94aa78e10ef4d7819a609",
                  "value":"0x0",
                  "gas":"0x247ec4",
                  "gas_used":"0x1c3235",
                  "input":"0xa1fe0e8d5e14560e314427eb9d0c466a6058089f672317c8e26719a770a709c3f2481e48000000000000000000000000000000000000000000000000000000000000004"
               },
               {
                  "type":"CALL",
                  "from":"0x87870bca3f3fd6335c3f4ce8392d69350b4fa4e2",
                  "to":"0x6b175474e89094c44da98b954eedeac495271d0f",
                  "value":"0x0",
                  "gas":"0x8510c",
                  "gas_used":"0x12a7",
                  "input":"0x23b872dd000000000000000000000000adc0a53095a0af87f3aa29fe0715b5c28016364e000000000000000000000000018008bfb33d285247a21d44e50697654f754e630000000000000000000000000000000000000000000009f256b1414eb2ea3170",
                  "output":"0x0000000000000000000000000000000000000000000000000000000000000001"
               }
            ]
         }
      ],
      "tx_id":"0x5eaaa56e1691f9d305343cfe3680c7705994ccb916c2666b1fab4cc560b22605",
      "tx_hash":"0x5eaaa56e1691f9d305343cfe3680c7705994ccb916c2666b1fab4cc560b22605",
      "timestamp":1721827031,
      "block_hash":"0x570ba481efbfe549e7fad3965af2aa913131af8cabb5516e7c51110130cbbf60",
      "block_number":20376644
   }
}

2. EVMFee Schema

The EVMFee schema represents the transaction fees on Ethereum and other EVM chains. It includes details about gas usage, price, and limits for the transaction. Supported protocols are:

bnb/mainnet
bnb/testnet
ethereum/mainnet
ethereum/sepolia
ethereum/hoodi
kaia/mainnet
kaia/testnet
optimism/mainnet
polygon/mainnet
polygon/amoy

The table below shows the schema breakdown:

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. The value is in the lowest denomination of the asset. For example: For ETH, the value is in `wei`. For BTC, the value is in `satoshi`.
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.

Examples

{
    "protocol": "ethereum",
    "network": "mainnet",
    "event_type": "unified_confirmed_tx",
    "chain_id":"eip155:1",
    "data": {
        "block_number": 19162260,
        "block_hash": "0xc678db39a15056113499816d38820477397ebe68b949eaf986e2db36ca0aeb75",
        "tx_id": "0xbc0d1ed22d11cec0f274f2033d5df4166debbdf0396513842c0717e5a70d72ae",
        "timestamp": 1707138395,
        "status": "success",
        "transfers": [
            {
                "asset": "native",
                "from": "0x3A024581D57D017453a67CF961771829B7F608F8",
                "to": "0x50E9198221E96b5aBF61159d892837587721549D",
                "value": 7000000000000000
            }
        ],
        "fee": {
            "gas_used": 21000,
            "gas_price": 14528344136,
            "gas_limit": 21000,
            "value": 305095226856000,
            "max_fee_per_gas": 15000000000,
            "max_priority_fee_per_gas": 1
        }
    }
}

{
    "protocol": "optimism",
    "network": "mainnet",
    "event_type": "unified_confirmed_tx",
    "chain_id": "eip155:1",
    "data": {
        "block_number": 126441614,
        "block_hash": "0x8ec67a7b960389dda7a8be49066ed72a8468e49d7ae0c8bbbb0ac61788a1d82d",
        "tx_id": "0x0362ab493db498d244e83d89249bf93c2945f21d86aaa43fab57db60cceb88bd",
        "timestamp": 1728482005,
        "status": "success",
        "transfers": [
            {
                "asset": "native",
                "from": "0xacD03D601e5bB1B275Bb94076fF46ED9D753435A",
                "to": "0x94b008aA00579c1307B0EF2c499aD98a8ce58e58",
                "value": 0
            }
        ],
        "fee": {
            "gas_used": 51838,
            "gas_price": 2415506,
            "gas_limit": 52232,
            "value": 125215000028,
            "max_fee_per_gas": 309914500,
            "max_priority_fee_per_gas": 309915
        }
    }
}

3. Multi Transfer Schema

The Multi Transfer schema is used when there are multiple transfers involving multiple signatures. Supported protocols are:

dogecoin/mainnet
dogecoin/testnet
litecoin/mainnet
litecoin/testnet

The table below shows the schema breakdown:

Field	Type	Description
asset	string	The asset type of the balance. For native tokens like Ethereum, the asset will be set to "native". For non-native tokens will have their denomination.
from	array of strings	The sender's account address.
value	integer	The value transferred. The value is in the lowest denomination of the asset.
event_name	string	A protocol-specific name for the transfer (if applicable). This field can provide more information on the type of transfer.

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
      }
   }
}

Unified Confirmed Transaction

Schema

1. Transfer Schema

Example

2. EVMFee Schema

Examples

3. Multi Transfer Schema

Example

👋 Need Help?