Skip to main content
GET
Try Cobo WaaS Skill in your AI coding assistant (Claude Code, Cursor, etc.). Describe your needs in natural language to auto-generate production-ready SDK code and debug faster 🚀

Authorizations

BIZ-API-KEY
string
header
required

The API key. For more details, refer to API key.

In the API playground, enter your API secret, and your API key will be accordingly calculated.

Path Parameters

chain_id
string
required

The chain ID, which is the unique identifier of a blockchain. You can retrieve the IDs of all the chains you can use by calling List enabled chains.

This operation currently supports the following chains only:

  • ETH: Ethereum mainnet.
  • SETH: Ethereum Sepolia testnet.
tx_hash
string
required

The transaction hash, which is the unique identifier of a transaction on the blockchain. You can retrieve the transaction hash of a transaction by calling Get transaction information.

You need to specify the hash with the 0x prefix.

Response

The information about a transaction receipt.

The information about a transaction receipt, which records the execution result of a transaction that has been included in a block.

All the numeric properties are returned as decimal values instead of the hexadecimal values used by the JSON-RPC interfaces of the chains. The properties that record on-chain amounts are returned as strings to avoid any precision loss.

chain_id
string
required

The chain ID, which is the unique identifier of a blockchain. You can retrieve the IDs of all the chains you can use by calling List enabled chains.

Example:

"ETH"

transaction_hash
string
required

The transaction hash, returned with the 0x prefix.

Example:

"0x239861be9a4afe080c359b7fe4a1d035945ec46256b1a0f44d1267c71de8ec28"

status
integer<int32>
required

The execution result of the transaction.

  • 1: The transaction was executed successfully.
  • 0: The transaction failed, for example, because it was reverted by the contract or ran out of gas.
Example:

1

block_number
integer<int64>
required

The number of the block that contains the transaction.

Example:

20123456

block_hash
string
required

The hash of the block that contains the transaction.

Example:

"0xc9ee947f8bb6027c161888bf0d004bec05e7c2beec7e6b187dc512174e438735"

transaction_index
integer<int64>
required

The index position of the transaction within the block.

Example:

42

from_address
string
required

The address that sent the transaction.

Example:

"0x1234567890abcdef1234567890abcdef12345678"

gas_used
string
required

The number of gas units consumed by the transaction.

Example:

"21000"

logs
object[]
required

The event logs emitted during the execution of the transaction, in the order in which they were emitted. The array is empty if the transaction emitted no logs. A maximum of 1,000 logs are returned. If the transaction emitted more logs, only the first 1,000 are returned and logs_truncated is true.

logs_truncated
boolean
required

Whether the event logs returned in logs were truncated.

  • true: The transaction emitted more than 1,000 logs and only the first 1,000 are returned.
  • false: All the logs emitted by the transaction are returned.
Example:

false

to_address
string | null

The address that received the transaction. The value is null if the transaction created a contract.

Example:

"0xdac17f958d2ee523a2206206994597c13d831ec7"

contract_address
string | null

The address of the contract created by the transaction. The value is null if the transaction did not create a contract.

Example:

"0xabcdef1234567890abcdef1234567890abcdef12"

cumulative_gas_used
string

The total number of gas units consumed by all the transactions up to and including this transaction in the block.

Example:

"8000000"

effective_gas_price
string

The gas price actually paid for each gas unit consumed by the transaction, in the smallest unit of the chain's native token. For example, the value is in wei for Ethereum.

Example:

"25000000000"

evm_transaction_type
integer<int32>

The transaction envelope type defined by the chain. This property describes the on-chain transaction format, not the Cobo transaction type returned by Get transaction information.

  • 0: A legacy transaction.
  • 1: An access list transaction, as defined in EIP-2930.
  • 2: A dynamic fee transaction, as defined in EIP-1559.
Example:

2

logs_bloom
string

The bloom filter of the event logs emitted during the execution of the transaction, which can be used to quickly check whether the transaction emitted a specific log. The value is a 256-byte hexadecimal string.

Example:

"0x00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000"