Latest Block
Chain ID:
atlantic-2
RPC Status:
labs
Activity
Assets & accounts
Developer tools
Chain & Data
Developer APIs
Contracts & Security
Smart contracts
Make contract code readable, enable ABI decoding and unlock Read / Write interactions across the explorer.
Choose your workflow
Start in the explorer, automate from your project, or let an MCP agent guide the process.
1. Contract to verify
Enter the deployed Sei EVM address. We check the on-chain bytecode when you submit.
2. Choose your build format
Start with the language used by your contract. Standard JSON is preselected because it preserves the exact build settings and resolves imports reliably.
Standard JSON
Preserves all compiler settings and gives the most reliable local match.
Best for: Hardhat, Foundry and production builds
Input: One compiler input JSON file
Single source
Paste or upload one flattened Solidity source file.
Best for: Small contracts and Remix exports
Input: One .sol file or pasted source
Multiple sources
Upload a project split across contracts, interfaces and libraries.
Best for: Projects without Standard JSON
Input: All source files and library addresses
Publish through Sourcify
Optional public verification for Solidity or Vyper Standard JSON builds.
Contract verification via Solidity (standard JSON input)
Specify the compiler with
and use that version instead of a nightly build.
Check it with