Verify with Parex Block Explorer
Last updated
Last updated
Verifying your deployed contract using flattened source code, JSON input, Sourcify and more.
Once verified, a smart contract or token contract's source code becomes publicly available and verifiable, creating transparency and trust.
We are here reproducing part of their documentation for contract validation.
Verification is available for both Solidity and Vyper contracts. Currently, there are 6 methods for verification using the Parex Blocscan UI.
To learn more about the smart contract verification Rust microservice and verification algorithm see this page for developers.
Once the code is deployed, you can view the transaction in detail on the Parex Block Explorer.
Go to the Verify contract page (Other -> Verify contract)
Enter in the contract address you received during deployment. The dropdown will show you several available verification options. Select the one you would like to use and continue.
Solidity (Flattened source code)
Solidity (Standard JSON input)
Solidity (Multi-part files)
Vyper (Multi-part files)
Vyper (Standard JSON input)
INFORMATION
To verify your smart contract, keep the following details handy:
Contract Name
Compiler
EVM version
Optimisation
The following table explains New Smart Contract Verification form in detail.
| Parameter | Description |
|---|---|
Contract Address | The |
Is Yul contract | Select if the contract is coded in Yul for efficiency. |
Include Nightly Builds | Select if you want to show nightly builds. |
Compiler | Derived from the first line in the contract |
EVM Version | |
Optimization Enabled | If you enabled optimization during compilation, select and enter the run value. 200 is the Solidity Compiler default value. Only change if you changed this value while compiling. |
Enter the Solidity Contract Code | |
Add Contract Libraries | Enter the name and 0x address for any required libraries called in the .sol file. You can add multiple contracts with the "+" button. |
Click the Verify and Publish button.
If all goes well, you will see a checkmark ✅ next to Code in the code tab, and an additional tab called Read Contract. The contract name will now appear in BlockScout with any transactions related to your contract.
Include nightly builds. You can choose Yes or No depending on your compiler.
Compiler. Choose the compiler version used to compile your smart contract. If you selected yes for nightly builds, use the compiler version rather than the build.
Standard Input JSON. Upload your Standard Input JSON file. File should follows solidity format and all the sources must be in Literal Content format, not a URL.
Click the Verify & publish button and wait for the response.
Contract Name: Name assigned to the contract.
Compiler: Select the compiler version used in the source code.
EVM Version: Select the correct EVM version if known, otherwise use default.
Contract Code: Copy and paste the contract code
Click the Verify and Publish button.
If all goes well, you will see a checkmark ✅ next to Code in the code tab, and an additional tab called Read Contract. The contract name will now appear in BlockScout with any transactions related to your contract.
If you receive the dreaded There was an error compiling your contract message this means the bytecode doesn't match the supplied sourcecode. Unfortunately, there are many reasons this may be the case. Here are a few things to try:
Double check the compiler version is correct.
Check all version digits - for example 0.5.1 is different from 0.5.10
Check that an extra space has not been added to the end of the contract. When pasting in, an extra space may be added. Delete this and attempt to recompile.
Copy, paste, and verify your source code in Remix. You may find some exceptions here.
The Hardhat verification plugin supports BlockScout. You can also choose to use the Sourcify plugin to verify with Sourcify from your hardhat environment.
Feel free to explore the Block Explorer further!
Select the correctif known, otherwise use default.
You may need to flatten your solidity code if it utilizes a library or inherits dependencies from another contract. We recommend or the .
