CREATE2 Predictor
The address CREATE2 (or CREATE) will deploy to.
Runs offline
Opcode
Enter the deployer address.
About create2 predictor
CREATE2 makes deployment addresses deterministic: the same deployer, salt and init code always produce the same address, on every chain. That is what lets a protocol know its address before deploying, and what lets a counterfactual wallet receive funds before it exists. Note that init code includes constructor arguments — change one and the address changes entirely. CREATE, by contrast, depends only on the deployer's nonce.
Common questions
How does CREATE2 decide an address?
From the deployer address, a salt, and the keccak of the init code — not from the deployer nonce. That is why a factory can publish a counterfactual address before the contract exists, and why this page can predict it offline.
What is the difference between CREATE and CREATE2?
CREATE derives the address from the deployer and its nonce, so it changes every deployment. CREATE2 derives it from deployer, salt and init code, so the address is stable for that triple. Both are shown when you supply each set of inputs.
Does predicting an address deploy the contract?
No. Prediction is pure hashing. Deployment still needs a transaction that runs CREATE2 with those arguments. An address that is predicted but never deployed is simply empty.