KAVACHOpen Decoder
TRANSACTION CLARITY, BEFORE CONFIRMATION

Read the Request.
Know the Permission.

Decode supported ERC-20 calls into readable explanations. Inspect addresses, amounts, and approval requests directly in your browser.

Open Decoder How It Works
01 — LOCAL BY DESIGN02 — PRECISE BY DEFAULT
SUPPORTED STANDARD CALLStransferapprovetransferFromDECODED LOCALLY
01 / THE METHOD

From hex to human.

Three direct steps to understand the arguments encoded in a supported function call.

Conceptual illustration of encoded data, not a live transaction.

01

Paste the calldata.

Enter the complete hexadecimal request. The selector identifies which supported standard signature it matches.

02

Inspect the decoded fields.

Read the encoded addresses and exact integer amount. Add decimals only if you know them.

03

Read what the request means.

Get a measured explanation of the arguments. The tool does not execute or simulate a transaction.

ANATOMY OF A REQUEST

Signals inside the string.

For supported calls, calldata begins with a four-byte selector followed by 32-byte ABI words. The visual is illustrative; it is not live transaction activity.

0xa9059cbb000000000000000000000000...
01FUNCTIONselector
02ADDRESSESABI words
03AMOUNTuint256
02 / SUPPORTED CALLS

Three signatures.
Clearer intent.

Select a call to see the fields KAVACH can interpret.

DIRECTIONAL TRANSFER
MATCHED FUNCTION

transfer(address,uint256)

Requests a transfer to a recipient address for an exact integer amount in base units.

Recipient addressAmount in base units

Conceptual illustration. The actual target contract determines behavior.

03 / PRODUCT PRINCIPLES

Useful by design.

01

Browser-only processing

Calldata is interpreted in your browser. No server-side decoder or transaction upload.

02

No wallet connection

Paste calldata directly. No signature, account, or wallet permission requested.

03

Exact integer handling

Amounts remain bigint values. Raw base units are always visible.

04

Downloadable explanations

Save a local text report with decoded arguments and limitations.

04 / THE BOUNDARY

Interpretation has limits.

A readable argument list helps you inspect a request. It does not establish what a target contract will do.

Open Decoder

Function selectors do not verify contract behavior. Different functions can share a selector.

A contract may implement unexpected behavior. KAVACH does not inspect contract code or blockchain state.

Balances, fees, execution success, and transaction effects are not predicted.

Token details are not automatically verified. Decoding is not a safety verdict.