Skip to main content
POST
analyze_transaction

Reading the result

The response example uses made-up values and shows selected fields. Fields vary by network and available data.
  • data contains a network-specific transaction analysis. In the EVM example, sender_info and receiver_info identify the addresses and any available risk findings.
  • logs_info contains decoded log details. gas_info includes gas price in wei and gas used and gas limit in gas units.
  • Solana, Tron, and Bitcoin return different fields for transfers, fees, or transaction inputs and outputs. Do not treat missing risk data as a clean assessment.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json
tx_hash
string
required

Full transaction hash or Solana signature. Include the network to disambiguate.

network
string
required

Network to query, for example ethereum. See Supported Networks for coverage.

Response

Decode and classify a single transaction (participants, value flow, risk flags). Fields vary by network and available data. Check for status: no_data, status: error, or an error field even when HTTP status is 200. See Errors & status.

Response fields depend on the network and available data. The example shows selected fields; see Reading the result for details.