Transaction Explainer
Any transaction in plain English: what happened, who got what, USD values, fee and revert reason.
Explain any mined transaction in plain English: what happened (swap, transfer, approval, NFT buy/sell/mint, wrap, contract deploy, failed + revert reason), the sender's net token changes with USD values, every token and native-coin movement, approvals granted, the function called (named from the verified ABI or a signature database, with decoded arguments) and the fee. Rule-based, no AI. Ethereum, Base, Arbitrum, Optimism, Polygon, BNB Chain.
What agents use it for
- Tell a user what a transaction they signed actually did
- Audit an agent's own on-chain actions after the fact
- Explain failed transactions with the revert reason
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
chain | "ethereum" | "base" | "arbitrum" | "optimism" | "polygon" | "bsc" | yes | Blockchain network (see allowed values) |
hash | string | yes | Transaction hash (0x + 64 hex) |
Call it
{
"name": "explain_transaction",
"arguments": {
"chain": "base",
"hash": "0x08ee682f9d01628aa8397e1ecc0c37cf47e468d67f711f3bc7e94addba0efffe"
}
}curl -i "https://api.ishob.com/v1/crypto/explain-tx?chain=base&hash=0x08ee682f9d01628aa8397e1ecc0c37cf47e468d67f711f3bc7e94addba0efffe"
Paid with x402: the first call returns HTTP 402 with the price; an x402 client (for example @x402/fetch or @x402/mcp) signs a USDC payment and retries. Calls that fail are not charged.
Connect the MCP server: setup for Claude, Cursor and other clients.