CREATE / CREATE2 Contract Address
Enter a deployer address and choose CREATE or CREATE2. The tool calculates the contract address from the nonce, or from the salt and init code, as a checksummed address.
Use the tool
Why this tool exists
Smart contract addresses are not random: they follow from who deploys them. With CREATE the address depends on the deployer and its nonce, and with CREATE2 it depends on the deployer, a salt and the hash of the init code. That makes it possible to know an address before deployment, which factories, wallets and cross-chain systems rely on. Developers need to check their expectations, for example that a factory will deploy to the address a front end shows. This tool follows EIP-1014 for CREATE2 and the RLP-based rule for CREATE, using Keccak-256 locally in your browser. You can supply either the init code itself or its hash. It does not look anything up on-chain, so it cannot tell whether an address is already in use.
How to use it
- Enter the deployer or sender address and choose CREATE or CREATE2.
- For CREATE, set the nonce; for CREATE2, set the salt and paste the init code in the second box.
- If you only have the init code hash, tick the checkbox, then read the checksummed address.
Frequently asked questions
How is the CREATE address derived?
As the last 20 bytes of keccak256(rlp([sender, nonce])). The nonce is the sender's transaction count for an account, so the same account gives a new address with each deployment.
How does CREATE2 differ?
The address is the last 20 bytes of keccak256(0xff ++ deployer ++ salt ++ keccak256(init_code)), so it does not depend on a nonce. The same deployer, salt and code always give the same address.
Can I paste the init code hash instead?
Yes. Tick 'Second input is already the init code hash' and paste the 32-byte hash. Otherwise the tool hashes the init code you give it.
Does the tool check the chain?
No. It computes the address only. Whether anything is deployed there, or whether the address has been used, needs a node or explorer.