Sign in
Onchain

Transaction Details by Hash

Look up one transaction by hash. Example: chain=ethereum with a 0x-prefixed 64-character hash.

All numeric fields are hex-encoded. Convert them with parseInt(hex, 16).

Supported chains: ethereum, polygon, bsc, arbitrum, optimism, base, avalanche, fantom, linea, cyber.

get/gateway/v1/onchain/tx

Query parameters

hashstring required

Transaction hash (0x-prefixed hex)

Example:0x5c504ed432cb51138bcf09aa5e8a410dd4a1e204ef84bfed1be16dfba1b22060

Transaction hash (0x-prefixed hex)

chain'ethereum' | 'polygon' | 'bsc' | 'arbitrum' | 'optimism' | 'base' | 'avalanche' | 'fantom' | 'linea' | 'cyber' required

Chain. Can be ethereum, polygon, bsc, arbitrum, optimism, base, avalanche, fantom, linea, or cyber.

Example:ethereum

Chain. Can be ethereum, polygon, bsc, arbitrum, optimism, base, avalanche, fantom, linea, or cyber.

includestring

Comma-separated enrichments to attach. Currently valid: labels — adds from_label and to_label fields with entity information for the from/to addresses.

Example:labels

Comma-separated enrichments to attach. Currently valid: labels — adds from_label and to_label fields with entity information for the from/to addresses.

Response

OK

$schemastring uri

A URL to the JSON Schema for this object.

Example response

{
  "$schema": "https://example.com/schemas/DataResponseOnchainTxItem.json"
}

Changes

No recorded changes to this endpoint across all 2 revisions of this API.