agentutility(7)$ man crypto-tx-explainer
/crypto-tx-explainer
PRICE / CALL
$0.04
USDC · base mainnet · scheme: exact
METHOD
POST
CLUSTER
edgemarketCATEGORY
uncategorized
STATUS
● live
NAME
crypto-tx-explainer — explain what actually happened in an on-chain transaction on ethereum, base, arbitrum, optimism, or polygon by sending its tx_hash
SYNOPSIS
POST https://x402.agentutility.ai/crypto-tx-explainer
Content-Type: application/json
X-PAYMENT: <signed-transferWithAuthorization>
{ ... }↳ first call →
402 Payment Required. Sign USDCtransferWithAuthorization, retry with theX-PAYMENT header.DESCRIPTION
Explain what actually happened in an on-chain transaction on Ethereum, Base, Arbitrum, Optimism, or Polygon by sending its tx_hash. It pulls the receipt and logs from public RPC providers and decodes status, native value moved, gas fee paid, ERC-20 and ERC-721 transfers, and which contracts got touched, labeling known ones like Uniswap routers, USDC, USDT, DAI, and WETH. Set explain: true and it also generates a plain-English summary of who sent what to whom, powered by Morpheus with a Venice fallback. Use it as a blockchain transaction explainer, crypto tx decoder, or on-chain forensics API for debugging agent transactions, building tx-history dashboards, or answering "what did I just sign".
INPUT — request schema
| property | type | description | req? |
|---|---|---|---|
| tx_hash | string | Transaction hash, 0x + 64 hex chars. | required |
| chain | string | 'ethereum', 'base' (default), 'arbitrum', 'optimism', or 'polygon'. enum: ethereum · base · arbitrum · optimism · polygon | optional |
| explain | boolean | Boolean, default false. When true, adds a 2-3 sentence plain-English explanation via LLM. | optional |
OUTPUT — response shape
| field | type | description |
|---|---|---|
| status | string | Transaction status, typically success or failed based on the receipt. |
| explanation | string | Plain-English summary of what the transaction did, generated by Venice when explain is true. |
EXAMPLES — two ways to call
EXAMPLE 1 · curl
curl -X POST https://x402.agentutility.ai/crypto-tx-explainer \
-H 'Content-Type: application/json' \
-d '{ }'first response =
402 Payment Required with payment requirements; sign + retry with X-PAYMENT.EXAMPLE 2 · mcp
# Install the MCP package for this endpoint's cluster npx -y @agentutility/mcp-<cluster> # Required: EVM private key with USDC on Base export X402_PRIVATE_KEY=0x... # Then call the crypto-tx-explainer tool from your MCP-aware agent.
MCP server handles payment automatically — your coding agent just calls the tool by name.
METADATA
- tags
- edge-marketblockchaintransaction-decoderevmerc20-transfersgas-feestx-explainer
- methods
- POST
- cluster
- edgemarket
- price
- $0.04 USDC per call
ADJACENT — other endpoints in edgemarket
| endpoint | description | price |
|---|---|---|
| bridge-rates | Compares cross-chain bridge quotes to find the cheapest route between chains, powered by LiFi. | $0.03 |
| dao-proposal-monitor | Monitors DAO governance proposals on Snapshot.org for any space. | $0.03 |
| ens-resolve | Resolves ENS names in both directions: forward (vitalik.eth to address) and reverse (address to primary ENS). | $0.03 |
| honeypot-check | Honeypot.is buy/sell simulation for any Base or Ethereum ERC-20. | $0.05 |
| token-honeypot | Detects whether an ERC-20 token is a honeypot by simulating a buy + sell via honeypot.is. | $0.05 |
| token-honeypot-api | Checks whether a token is a honeypot, testing sellability, buy tax, sell tax, proxy risk, owner risk, and token-trading warnings. | $0.05 |
| token-honeypot-check | Checks whether an ERC-20 token is a honeypot by simulating buy and sell behavior through honeypot.is. | $0.05 |
| wallet-pnl | Computes wallet token P&L with FIFO cost basis for any (wallet, ERC-20, chain) triple. | $0.05 |
SEE ALSO