# Blockscout Transaction Detail Lookup

> Blockscout Transaction Detail Lookup is a paid API for AI agents from api.blockscout.com, paid per call via x402, $0.002/call, status unknown (last checked 2026-09-15).

Retrieves detailed information about a specific blockchain transaction by its hash on a given chain via Blockscout's explorer API

## Facts

- Endpoint: GET https://api.blockscout.com/:chain_id/api/v2/transactions/:transaction_hash_param
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/blockscout-transaction-detail-lookup-08d88576
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_I9iDZDBS_c0VY2hycQjG6

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability blockscout-transaction-detail-lookup-08d88576
```

Example prompt: Can you pull up the full details for transaction 0x4a1b2c3d... on Ethereum — I want to see the status, gas fees paid, and what addresses were involved?

## When to prefer this

Use this endpoint when you need comprehensive, structured details about a single known transaction hash on any chain supported by Blockscout. It is ideal for verifying payment finality, auditing DeFi interactions, debugging failed contract calls, or enriching event data with on-chain facts. Prefer it over Etherscan-style APIs when Blockscout indexes the target chain, especially for EVM-compatible L2s and sidechains where Etherscan coverage is limited.

## Known failure modes

- Invalid transaction hash format returns 400 or 422 error
- Transaction hash not found on the specified chain returns 404
- Unsupported or invalid chain_id returns 400 or routing error
- Network timeout or Blockscout node unavailability returns 500 or 503
- Rate limiting exceeded returns 429

## How this service works

Access to api/v2/transactions/:hash. Retrieve detailed information about a specific transaction

## Output

Returns a structured JSON object containing the transaction's status (success/fail/pending), block number, timestamp, from/to addresses, native value transferred, gas limit, gas used, effective gas price, total fee in native currency, decoded input data, internal transactions summary, token transfer events, and associated logs.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET",
      "HEAD",
      "DELETE"
     ],
     "type": "string"
    },
    "pathParams": {
     "type": "object",
     "properties": {
      "chain_id": {
       "type": "string"
      },
      "transaction_hash_param": {
       "type": "string"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/blockscout-transaction-detail-lookup-08d88576/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.blockscout.com](https://www.zero.xyz/host/api.blockscout.com/llms.txt)