# EVM Transaction Decoder

> EVM Transaction Decoder is a paid API for AI agents from api.vextorium.com, paid per call via x402, $0.004/call, status unknown (last checked 2026-10-16).

Decodes an EVM transaction by hash, returning the called method with parameter names, token transfers, value, fee, status, revert reason, and address labels across multiple EVM networks.

## Facts

- Endpoint: POST https://api.vextorium.com/tx-decodificada-pago?utm_source=zero.xyz
- Price: $0.004/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/evm-transaction-decoder-2c27b7df
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ku9tl2csDkIdXjF__NrHC

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 evm-transaction-decoder-2c27b7df -d '<json body>'
```

Example prompt: Can you decode this Ethereum transaction for me — hash 0xabc123...def456 — and tell me what method was called, what tokens moved, and whether it succeeded or reverted?

## When to prefer this

Use this endpoint when you need a human-readable breakdown of any EVM transaction — especially when you want decoded method names and parameters (not just raw calldata), token transfer lists, and labeled address names. It covers six major EVM networks (Ethereum, Base, Arbitrum, Optimism, Polygon, zkSync) in a single call. Prefer it over raw RPC calls when you need enriched, interpreted data rather than raw hex output.

## Known failure modes

- Invalid or malformed transaction hash returns an error
- Transaction hash not found on the specified network returns null or error
- Unverified contract ABI means method and parameters cannot be decoded (returned as null)
- Unsupported network value (outside the enum) causes a validation error
- Network mismatch (hash exists on a different chain than specified) returns not found

## How this service works

An EVM transaction explained: method called and its decoded parameters with names (when the contract is verified), token transfers it triggered, value, fee, status, revert reason and names of the addresses involved.

## Output

A JSON object containing the decoded method name and its named parameters (if the contract is verified), an array of token transfers triggered by the transaction, the native value transferred, the fee in native token, the transaction status (success/failure), the revert reason if applicable, ENS names and labels for addresses involved, block number, timestamp, confirmations, and the network.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "red": {
   "enum": [
    "ethereum",
    "base",
    "arbitrum",
    "optimism",
    "polygon",
    "zksync"
   ],
   "type": "string"
  },
  "hash": {
   "type": "string"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/evm-transaction-decoder-2c27b7df/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.vextorium.com](https://www.zero.xyz/host/api.vextorium.com/llms.txt)