Contract address calculator (CREATE and CREATE2)
Find out where a contract will land before it is deployed: from a deployer and its nonce, or from a factory, a salt and the init code or its hash.
A plain CREATE address depends only on the deployer and its nonce, so you can predict every contract an account will deploy. CREATE2 (EIP-1014) uses the factory address, a 32-byte salt and the keccak-256 of the init code instead, which is how counterfactual wallets and deterministic deployments work.
Give either the init code or its hash for CREATE2. Results are EIP-55 checksummed.
AI agents can run this through the SwapChan MCP tool create_address. Set up MCP
FAQ
- Which nonce do I use?
- The deployer's transaction count at the time of the deploy. For a contract deployer, it is the contract's own nonce, which starts at 1.
- Do I need the full init code for CREATE2?
- No. The keccak-256 hash of the init code is enough.
- Is it safe?
- Yes. It only reads public data you paste. Nothing is stored or logged, and you never need a private key or seed phrase here.