Contract Source
Verified source — or the fact it was never published — on 90 indexed networks.
Reads public data
Paste a contract address. Nothing connects and nothing is signed.
About contract source
A verified contract is one whose published source has been compiled and matched against the deployed bytecode, so you can read what it actually does. An unverified contract has never had its source published, and approving one is trusting a stranger with no way to check. Proxies deserve particular attention: the code at the address you are looking at may only forward calls to an implementation that whoever controls the proxy can replace. Verified source says what runs — not whether that is in your interest.
Common questions
How do I read a verified contract source?
Paste the address on a network we index. If the explorer has verified source, this shows it; if not, it says the source was never published — which is itself useful before you approve an unknown spender.
Does verified source mean the contract is safe?
No. Verification only means the published Solidity matches the bytecode. Malicious logic can be verified in full public view. Unverified bytecode is opaque; verified bytecode can still be hostile.
Which networks are covered?
The indexed set this site already reads for portfolios and explorers — on the order of ninety networks where a Blockscout-style or equivalent source API answers. A chain without verification data returns that fact rather than inventing source.