Transaction Calldata Plain-English Reader

WHAT IT DOES

Transaction Calldata Plain-English Reader takes raw transaction calldata (the hex string you're about to sign) and translates it into plain English. It decodes the function signature (method ID), extracts each parameter by type (address, uint256, bool, bytes), and shows you what each value represents. If the function is in the built-in database, it tells you what the function does and what each parameter means. An AI layer then provides a plain-English explanation of what the calldata is actually asking for. No more staring at hex strings—you get a human-readable translation of the data before you sign.

HOW TO USE

Connect your EVM wallet using the BotGentz wallet bridge. Select your network. Paste a transaction hash to fetch and decode its calldata, or paste raw hex calldata directly. Click "Read"—the tool extracts the method ID, matches it against the signature database, decodes all parameters, and generates an AI explanation. Results show you the target address, value, method ID, function name, parameter list with decoded values, raw calldata preview, risk flags, and a plain-English explanation of what the calldata means. No transaction is ever submitted—this tool is read-only and free.

TECHNICAL MECHANISM

The app uses the injected BGWallet bridge to access the EVM provider via ethers.js v5.7.2. Transaction hashes are fetched via provider.getTransaction(). The raw call data (hex string) is parsed to extract the method ID (first 4 bytes, 8 hex characters). This method ID is looked up in a built-in signature database covering common ERC20 functions (transfer, approve, transferFrom, allowance, balanceOf), ERC721 functions (ownerOf, safeTransferFrom, transferFrom, setApprovalForAll), and admin functions (owner, transferOwnership, renounceOwnership, selfdestruct, pause, unpause, withdraw). Parameter decoding follows the ABI encoding rules: addresses are extracted from 64-hex chunks, uint256 values are converted using ethers.BigNumber, and booleans are checked against canonical hex values. The decoded function name, parameters, method ID, and raw data are passed to the AI bridge (BGAI.generate), which returns a plain-English explanation capped at 1,024 tokens.

WHAT IT CANNOT SEE

This tool cannot detect malicious intent hidden in contract bytecode—it reads only the calldata visible on-chain. It cannot verify that the resolved function name from the signature database matches the actual contract implementation—any contract can implement a function with the same method ID but different behavior. It cannot verify off-chain intent or consequences. It cannot detect cross-contract exploits, reentrancy vulnerabilities, or front-running. It cannot decode custom data structures or complex nested types beyond basic ABI types (address, uint256, bool, bytes). The AI explanation is generated from the provided data and may miss nuanced attack patterns not present in the calldata itself.

PLEASE NOTE

Supports EVM-compatible chains only—Ethereum, Sepolia, Polygon, Mumbai, Optimism, Arbitrum, and any network the wallet bridge connects to. The signature database is built-in and covers the most common functions—if a function is not in the database, the tool will show the method ID and raw data but cannot provide a function name. Explanations are AI-generated and should be treated as assists, not authoritative audits. Always review the transaction details in your wallet's own signature prompt before approving. The wallet's signature step is the only protection that actually gates any action—this tool is informational and does not replace that safeguard. Free to use, no API keys required.