Unified Confirmed Transaction Log
This event is triggered when:
- A log is emitted from a smart contract execution on an EVM-based blockchain.
- It captures details related to the event logs generated during a transaction execution.
Supported Protocols
bitcoincash/testnetbnb/mainnetbnb/testnetdogecoin/testnetethereum/mainnetethereum/sepoliaethereum/hoodikaia/mainnetkaia/testnetlitecoin/testnetmonad/mainnetmonad/testnetoptimism/mainnetpolygon/mainnetpolygon/amoytron/mainnettron/nile
Schema
{
"data": {
"block_number": "integer",
"block_hash": "string",
"tx_id": "string",
"tx_hash": "string",
"timestamp": "integer",
"status": "string",
"transfers": [
"array"
]
}
}| Field | Type | Description |
|---|---|---|
block_hash | string | (Required) The block hash. |
block_number | integer | (Required) The block number. |
tx_id | string | (Required) The transaction identifier, such as the transaction hash or other unique identifier. |
tx_hash | string | The transaction hash. |
timestamp | integer | (Required) The UNIX timestamp when the block was mined/validated. |
status | string | (Required) The transaction status when available. The default status for successful transactions is success and failed for failed transactions. |
transfers | array of transfers | An array of transfers decoded from the log. Each entry has asset (the emitting contract address), from, to, and value. |
This schema applies to the UNIFIED_V1 and UNIFIED_V1_RAW templates. ALL_DATA returns the chain's native log payload unmodified, with its own fields, shown below per protocol.
InfoBitcoin Cash, Dogecoin, Litecoin, BNB Smart Chain, Kaia, and Tron aren't shown below yet. They're supported for this event type, but a payload example hasn't been captured for them.
Examples
Ethereum
The native log's decoded[] array is decoded per the emitting contract's event signature, so field names vary (from/to/value for a standard Transfer event). decodingSource reports how the log was decoded, ContractAbi means a known ABI was used, BruteForceOtherAbi or BruteForceStandardAbi mean the field names were inferred. The unified transfers[] entry always normalizes this down to asset, from, to, and value regardless of decodingSource.
{
"chain_id": "eip155:1",
"protocol": "ethereum",
"network": "mainnet",
"event_type": "unified_confirmed_tx_log",
"data": {
"block_number": 19639919,
"block_hash": "0x3160a4d48293477f4b1b156700efb626a34373953f43220f68cba7c97a983e0f",
"tx_id": "0xdd984b4e5e06cf9bccda14f216cf9c546d7ac7468650f5207d07fc03682525a2",
"tx_hash": "0xdd984b4e5e06cf9bccda14f216cf9c546d7ac7468650f5207d07fc03682525a2",
"timestamp": 1712929631,
"status": "success",
"transfers": [
{
"asset": "0xdAC17F958D2ee523a2206206994597C13D831ec7",
"from": "0x8b7b59Ee336c076cd85bC43cD402B5b0526a69e4",
"to": "0xf89d7b9c864f589bbF53a82105107622B35EaA40",
"value": 2500000000
}
]
}
}👋 Need Help?
Contact us through email or our support page for any issues, bugs, or assistance you may need.
Updated 5 days ago