Skip to main content

Exploring Contract Page

Updated over 3 weeks ago

The Contract tab provides a complete breakdown of any verified smart contract, accessible through three sub-tabs: Code, Read Contract, and Write Contract. A green tick icon next to the Contract tab title indicates that the contract is verified; if the green tick is absent, the contract is not verified.

Contract page on Routescan

Code Sub-Tab

The Code sub-tab displays the contract's verified status and associated details in a structured format, along with several data windows.

  • Contract Source Code Verified Status: Indicates whether the contract's source code has been verified, showing either Partial Match or Full Match if verified.

  • Creation Timestamp: Displays the date and time when the contract was created.

  • Contract Details:

    • Contract Name: Name of the token contract.

    • Compiler Version: Version of the compiler used to compile the contract.

    • Optimization Enabled: Indicates whether code optimization was enabled during compilation.

    • Other Settings: Additional compiler settings, such as the default EVM version.

  • Code Window: Shows the full source code of the contract.

  • Contract ABI Window: Displays the Application Binary Interface (ABI) of the contract, used for interacting with the contract programmatically.

  • Contract Creation Code Window: Shows the bytecode used to deploy the contract.

  • Constructor Arguments Window: Lists the ABI-encoded constructor arguments, extracted as the last bytes of the Contract Creation Code, used during contract deployment.

  • Contract Security Audit: Provides results or details of any security audits performed on the contract.

ℹ️ Important Note: Not all security audits may be listed, and users should independently verify audit information. Routescan does not take responsibility for the completeness or accuracy of the audit details provided.

Contract code sub-tab on Routescan
Code sub-tub ABI, Creation code and Constructor Arguments on Routescan

Read Contract Sub-Tab

The Read Contract sub-tab allows you to interact with the token's smart contract by querying its public functions and retrieving data directly from the blockchain without executing transactions.

  • Function List. Displays a list of the contract's public read-only functions, such as retrieving the total supply, balance of an address, or token decimals.

  • Input Fields. Provides fields for you to input parameters required by the functions (e.g., an address to check its balance).

  • Query Results. Shows the output of the queried function, providing real-time data from the contract, such as the current token balance or allowance for a specific address.

Read contract sub-tab on Routescan

Write Contract Sub-Tab

ℹ️ Important Note: Executing write contract functions is a sensitive operation that can have significant consequences on the blockchain and user's address. Users should proceed with caution and only perform these actions if they fully understand the implications and functionality of the contract.

The Write Contract sub-tab enables you to interact with the token's smart contract by executing its write functions, allowing actions that modify the blockchain state, such as transferring tokens or approving allowances.

  • Function List. Displays a list of the contract's public write functions, such as transfer, approve, or other state-changing operations.

  • Input Fields. Provides fields for you to input required parameters, like the recipient address and amount for a transfer.

  • Transaction Execution. Allows uoi to connect a wallet and submit a transaction to the blockchain, executing the selected function and altering the contract's state, such as transferring tokens or setting allowances.

  • Write Contract Simulation. Routescan's Simulation feature helps you manage transaction risk. It lets you safely test a transaction in a simulated environment before you sign and broadcast it to the blockchain. To learn more, dive into our Write Contract Simulation.

Write contract sub-tab on Routescan
Did this answer your question?