calldata decoder
paste a transaction's input data and an ABI, and decode the function call into its 4-byte selector, name, signature, and typed arguments — for any EVM contract, entirely in your browser.
what is transaction calldata?
every EVM transaction that calls a contract carries an input data field — the calldata. it begins with a 4-byte function selector (the first four bytes of the keccak-256 hash of the function signature) followed by the arguments, ABI-encoded into 32-byte words. decoding it turns that opaque hex blob back into a readable call: which function was invoked and with what values.
how to decode calldata here
paste the contract's ABI (or keep the ERC-20 ABI loaded by default), then paste the full input data — selector plus encoded arguments, whitespace is ignored so explorer copies work. the tool matches the selector against the ABI's functions and decodes each argument by type, including addresses, integers, booleans, bytes, strings, arrays, and tuples. a bare 4-byte selector resolves to its function; a 32-byte value resolves an event topic.
decoding runs locally with viem; nothing is uploaded. to read and write functions, decode revert errors, and look up selectors in one place, open the read · write workbench.