Contract safety · ERC-20, ERC-721, ERC-4626
Token standard checker
Check whether a deployed contract really implements ERC-20, ERC-721 or ERC-4626.
Contract to check
Everything is read straight from the deployed bytecode and live calls. No source code needed.
The address the token is deployed at.
Pick the standard the contract claims to implement.
Where the contract is deployed.
No verdict yet
Enter a contract address and you get a pass or fail for the standard, then a line for every entry point the standard requires.
About this tool
A token standard checker tests whether a deployed contract really implements the standard it claims. Pick ERC-20, ERC-721 or ERC-4626 and enter the contract address. The tool calls the standard's read functions over a public RPC, looks for the selectors of functions it cannot safely call in the deployed bytecode, follows EIP-1967 proxies, and checks ERC-165 support where the standard requires it.
Common questions
Does passing the check mean a token is safe?
No. It confirms the required functions exist and respond, not that they behave honestly. A token can pass and still have an owner mint, transfer fees, a blocklist or an upgradeable implementation. Read the verified source before you trust it with money.
Why check the bytecode instead of the ABI?
An ABI is only a description that anyone can write. The deployed bytecode is what actually runs, so finding a function's 4-byte selector in it is stronger evidence that the function exists.
Does it check ERC-1155?
No. It covers ERC-20 fungible tokens, ERC-721 NFTs and ERC-4626 tokenized vaults.