# Foundry Base Transaction Explainer

> Foundry Base Transaction Explainer is a paid API for AI agents from minty-sprout.onrender.com, paid per call via x402, $0.002/call, status unknown (last checked 2026-11-01).

Decodes a Base chain transaction hash into human-readable details: status, block, gas, ETH value, method selector, contract creation, and decoded ERC-20 token transfers.

## Facts

- Endpoint: POST https://minty-sprout.onrender.com/v1/base-tx-explain?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-01
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/foundry-base-transaction-explainer-fa1e0044
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_kzkUUMEmAvJ-NGDDI5_xZ

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 foundry-base-transaction-explainer-fa1e0044 -d '<json body>'
```

Example prompt: Can you explain what happened in this Base transaction — 0x920b38d85c8dccaa06e1dae783f057feebd571260aefb7f055a04c60b708df1f — did it succeed, how much gas was used, and were any tokens transferred?

## When to prefer this

Choose this endpoint when you need deterministic, no-hallucination decoding of a specific Base chain transaction by hash — especially when you need ERC-20 transfer details decoded with human-readable token symbols and amounts. Prefer this over general blockchain explorers when operating in an agent workflow that requires structured JSON output and pays per-call via x402.

## Known failure modes

- Transaction hash not found on Base chain — returns found: false
- Invalid hash format (not 0x + 64 hex chars) — likely returns validation error
- Transaction is too recent and not yet indexed — may return not found
- Network or RPC timeout — service unavailable error
- Non-Base chain transaction hash provided — will not be found

## How this service works

Base transaction explained from the chain: success or reverted, block and time, from, to, ETH value, method selector, gas used and fee, contract created, and every ERC-20 transfer decoded with token symbol and amount. Input: 0x transaction hash. Deterministic, no LLM.

## Output

A JSON object containing: transaction found flag, success/reverted status, block number, from and to addresses, ETH value, method selector, gas used, fee in ETH, contract created address (if any), and an array of decoded ERC-20 token transfers each with from, to, token contract address, token symbol, and amount.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "input": {
   "type": "string",
   "maxLength": 8000,
   "description": "Base transaction hash, 0x + 64 hex characters"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "to": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
  "from": "0xE72f0Af4CF41356d433723547F1412cA27FBB1B8",
  "hash": "0x920b38d85c8dccaa06e1dae783f057feebd571260aefb7f055a04c60b708df1f",
  "block": 53338596,
  "found": true,
  "status": "success",
  "fee_eth": 0.00000103,
  "gas_used": 103342,
  "value_eth": 0,
  "method_selector": "0xe3ee160e",
  "token_transfers": [
   {
    "to": "0x11DCED0487cA3E7d9032029DCb302253ccF4e0DE",
    "from": "0x87C407Ff6765C9f956A1025a78B05f48E9b7A65C",
    "token": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
    "amount": 0.005,
    "symbol": "USDC"
   }
  ]
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/foundry-base-transaction-explainer-fa1e0044/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from minty-sprout.onrender.com](https://www.zero.xyz/host/minty-sprout.onrender.com/llms.txt)