1
Input — Paste the contract address and hex data field from your wallet (visible in MetaMask before signing), or drop in the full JSON transaction object.
2
ABI lookup — The decoder fetches the contract's verified ABI from the Mezo explorer. If none is found and the address is a known Mezo token, it falls back to the standard ERC-20 ABI.
3
Decoding — The first 4 bytes of the calldata (the function selector) are matched against the ABI. The remaining bytes are unpacked into typed parameters using ethers.js.
4
Output — Shows the function name, each parameter with its type and decoded value, token amounts formatted with proper decimals, and every address linked to the Mezo explorer. The JSON tab also surfaces from, chain, native value, gas, and nonce.
Decoding requires the contract to be verified on the Mezo explorer, or to be a standard ERC-20. Unverified contracts with custom ABIs cannot be decoded. All requests go directly from your browser — nothing is logged or stored.