ERC-20 approval decoder
Make the approval readable.
Decode three common token-call shapes offline and compare the recipient, spender and amount with your own expectations.
Use my own recordsLocal processing · No account · No wallet connection
What would you like to check?
Choose a fictional scenario to run it immediately, then change the assumptions.
Make it your own
Edit the form or import the example-shaped JSON. Input reference
Edit the inputs
Inputs stay in this tab and clear on reload. No automatic upload or wallet access. Maximum 128 KiB.
Reports include your record labels. Review them before sharing.
Report text for manual copy
From your records to a reviewable result
- Copy a prepared call from a source you already control. Do not paste private keys or seed phrases.
- Enter the expected destination and atomic-unit limit from your intended action.
- Review differences and use your trusted wallet/simulator for the actual decision.
Where this tool fits
A no-wallet, exact-amount second look at a prepared call, with explicit unsupported states and a portable review report.
Scope: No chain simulation, malicious-contract detection, token identity lookup, balance inspection or safety verdict.
钱包调用解释:可直接使用表单,也可导入 JSON。先运行虚构示例理解结果,再切换到自己的材料。输入仅在当前页面处理。查看中文说明。
Compare with established tools
A real security product or simulator has chain context this decoder lacks. A known selector and an empty flag list cannot show that a contract is safe.
Official product descriptions reviewed 19 September 2026. These are alternatives, not partners or endorsements.
- Blockaid
Onchain security, transaction protection, monitoring and threat intelligence.
- Tenderly
Transaction simulation with decoded traces, gas estimates and asset changes.
- ERC-20 specification
Defines fungible-token transfers and allowances; implementation behavior still matters.
What does Call Lens do?
Call Lens decodes supported token-call shapes locally and compares the recipient, spender and atomic amount with your expectations. It distinguishes ERC-20 allowances from ERC-721 token IDs using the declared standard. It never connects a wallet or evaluates contract safety.
By the AGI Scorecard team. Method and sources reviewed . Read the method.
Questions before you start
Why is approve(address,uint256) ambiguous?
ERC-20 and ERC-721 share that selector but use the integer differently: a fungible-token allowance versus a token ID. The declared standard is necessary context and must be verified against the actual contract.
Is Call Lens free, and do I need a wallet?
All current functions are free beta. No account, wallet connection, subscription or model API key is needed. No chain simulation, malicious-contract detection, token identity lookup, balance inspection or safety verdict.
Can I use my own records and keep them private?
Yes. Enter records, import JSON or paste CSV into record groups. Inputs and comparison snapshots stay in this browser tab. Share-example links contain only a public scenario name. Review downloaded reports before sharing your records.
Use this workflow in your AI assistant
Connect the MCP server to read sources and run these calculations from a supported client. Remote calls send parameters to the server; the browser worksheet remains local.
Get the MCP connection and citation guide