# x402helper.xyz Transaction Explain

> x402helper.xyz Transaction Explain is a paid API for AI agents from x402helper.xyz, paid per call via x402, $0.0156/call, status unknown (last checked 2026-10-31).

Fetches and explains an EVM blockchain transaction given its hash, returning structured details about what the transaction did.

## Facts

- Endpoint: GET https://x402helper.xyz/89e509/tx/explain?utm_source=zero.xyz
- Price: $0.0156/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-31
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402helper-xyz-transaction-explain-08d1fabd
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_VY9WhcgBBlP9jzzx071_v

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 x402helper-xyz-transaction-explain-08d1fabd
```

Example prompt: Can you explain what happened in this Ethereum transaction — 0x3a7f...4c9b — it was on the Base network?

## When to prefer this

Use this endpoint when you need a human-readable or structured explanation of a specific EVM transaction identified by its hash, especially across a wide range of supported networks (Base, Ethereum, Arbitrum, Optimism, Polygon, BNB, Avalanche, Gnosis, Linea, Scroll, Celo, Mantle). Prefer this over block explorer scraping when you need programmatic JSON output rather than an HTML page.

## Known failure modes

- Invalid or malformed transaction hash returns an error
- Transaction hash not found on specified network
- Unsupported network name causes validation failure
- Missing required 'hash' query parameter returns error
- Network congestion or RPC timeout causes delayed or failed response

## How this service works

X402 micropayments server — AI agents pay USDC for OFAC screening, rates, and billing verification.

## Output

Returns a JSON object with a 'success' boolean and a 'result' object containing structured details explaining what the given EVM transaction did — including transfer amounts, involved addresses, contract calls, and other decoded on-chain activity.

## 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"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "hash"
     ],
     "properties": {
      "hash": {
       "type": "string",
       "default": null,
       "description": "Transaction hash (0x + 64 hex characters)"
      },
      "network": {
       "enum": [
        "base",
        "ethereum",
        "arbitrum",
        "optimism",
        "polygon",
        "bnb",
        "avalanche",
        "gnosis",
        "linea",
        "scroll",
        "celo",
        "mantle"
       ],
       "type": "string",
       "default": null,
       "description": "EVM network to read from (default base)"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "result": {},
  "success": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x402helper-xyz-transaction-explain-08d1fabd/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402helper.xyz](https://www.zero.xyz/host/x402helper.xyz/llms.txt)