> For the complete documentation index, see [llms.txt](https://zokyo-auditing-tutorials.gitbook.io/zokyo-automated-tools/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://zokyo-auditing-tutorials.gitbook.io/zokyo-automated-tools/mastering-slither-a-comprehensive-guide-to-smart-contract-vulnerability-detection/analyzing-smart-contracts-already-deployed-on-main-nets.md). # Analyzing Smart Contracts Already Deployed On Main-nets {% hint style="info" %} [**Book an audit with Zokyo**](https://www.zokyo.io/) {% endhint %} ### **Introduction** In the realm of smart contract security and blockchain analytics, the ability to analyze contracts deployed on various networks is invaluable. Slither, a powerful static analysis tool, is adept at scrutinizing smart contracts across different networks such as Ethereum Mainnet, Arbitrum, and others. This capability enables a broader and more nuanced analysis, accommodating the diverse landscapes where smart contracts operate. This tutorial aims to guide you through the process of analyzing smart contracts on various networks using Slither, elucidating the essential commands and practices to execute this task effectively. ### **Getting Started** Before proceeding, ensure that Slither is properly installed and configured in your development environment, and you have essential network details like contract addresses. ### **Analyzing Contracts on Ethereum Mainnet** #### **Command Syntax** To analyze a contract on Ethereum Mainnet, use the following syntax: ```bash slither ``` **Example:** ```bash slither 0x8FE00a685Bcb3B2cc296ff6FfEaB10acA4CE1538 ``` This command tells Slither to perform a static analysis on the contract deployed at the specified address on Ethereum Mainnet. ### **Analyzing Contracts on Arbitrum Network** #### **Command Syntax** For contracts deployed on networks like Arbitrum, you can specify the network in the command like this: ```bash slither arbi: ``` **Example:** ```bash slither arbi:0xc20DE37170B45774e6CD3d2304017fc962f27252 ``` This syntax directs Slither to target the Arbitrum network for the analysis, using the specified contract address. Here are some common Ethereum networks and their identifiers: * **Ethereum Mainnet** * **Example:** `slither ` * **Ropsten Testnet** (`rop`) * **Example:** `slither rop:` * **Rinkeby Testnet** (`rinkeby`) * **Example:** `slither rinkeby:` * **Goerli Testnet** (`goerli`) * **Example:** `slither goerli:` * **Kovan Testnet** (`kovan`) * **Example:** `slither kovan:` * **Arbitrum** (`arbi`) * **Example:** `slither arbi:` * **Binance Smart Chain** (`bsc`) * **Example:** `slither bsc:` * **Polygon (Matic) Mainnet** (`polygon`) * **Example:** `slither polygon:` * **xDai Chain** (`xdai`) * **Example:** `slither xdai:` * **Fantom Opera** (`fantom`) * **Example:** `slither fantom:` * **Avalanche C-Chain** (`avalanche`) * **Example:** `slither avalanche:` * **Huobi ECO Chain (Heco)** (`heco`) * **Example:** `slither heco:` * **Optimistic Ethereum** (`oeth`) * **Example:** `slither oeth:` * **Moonbeam** (`moonbeam`) * **Example:** `slither moonbeam:` Remember always to replace `` with the actual address of the contract you want to analyze. Note that the availability of networks might depend on the Slither version and the specific configuration you are using. Make sure to consult the official documentation for any updates or additions to the network list and their respective identifiers. #### **Analyzing Contracts on Different Networks with Slither: A Detailed Guide** ### **Introduction** In the realm of smart contract security and blockchain analytics, the ability to analyze contracts deployed on various networks is invaluable. Slither, a powerful static analysis tool, is adept at scrutinizing smart contracts across different networks such as Ethereum Mainnet, Arbitrum, and others. This capability enables a broader and more nuanced analysis, accommodating the diverse landscapes where smart contracts operate. This tutorial aims to guide you through the process of analyzing smart contracts on various networks using Slither, elucidating the essential commands and practices to execute this task effectively. ### **Getting Started** Before proceeding, ensure that Slither is properly installed and configured in your development environment, and you have essential network details like contract addresses. ### **Analyzing Contracts on Ethereum Mainnet** #### **Command Syntax** To analyze a contract on Ethereum Mainnet, use the following syntax: ```bash slither ``` **Example:** ```bash slither 0x8FE00a685Bcb3B2cc296ff6FfEaB10acA4CE1538 ``` This command tells Slither to perform a static analysis on the contract deployed at the specified address on Ethereum Mainnet. ### **Analyzing Contracts on Arbitrum Network** #### **Command Syntax** For contracts deployed on networks like Arbitrum, you can specify the network in the command like this: ```bash slither arbi: ``` **Example:** ```bash slither arbi:0xc20DE37170B45774e6CD3d2304017fc962f27252 ``` This syntax directs Slither to target the Arbitrum network for the analysis, using the specified contract address. ### **Customizing Your Analysis** Slither comes with various options that allow you to customize the analysis based on your needs, such as specifying particular detectors or printing specific information. Explore Slither’s documentation to dive deeper into these customization options. ### **Conclusion** Utilizing Slither for the analysis of contracts on diverse networks enhances the breadth and depth of your smart contract security practices. Armed with the commands and methodologies outlined in this tutorial, you’re equipped to navigate the analysis process across various networks seamlessly. This flexibility, coupled with Slither’s robust static analysis capabilities, enables a comprehensive evaluation of smart contracts, fostering enhanced security and analytical insights. Remember always to tailor your analysis based on the network and the specific characteristics of the contract under scrutiny.