# Contracts This is a one of a kind tool. It allows you to see: * All **deployed tokens** per block. * **Proxy** Status * Contract **values**. * **Functions' signatures** and **names**. * Best effort approach at calculating **function safety** based on historical safe contracts. * **Checksum** tracking. **All of this even for unverified contracts, meaning that the source code is not available!** ### How is this possible? By analyzing opcodes extracted from the bytecode, we can deconstruct the compiler flow and try to find where functions end, jump or read/write data, and compute their unique method's signature.\ Then, consulting an huge functions db, we can extract the name.\ Sometimes, the name will not be available, and you will see the signature in the "Unknown" category! ### How does the security check work? Secret sauce.\ This is a best effort approach so it's prone to failure sometimes.\ It's not 100% accurate end most likely never will, but it gives you a good first look at what each function is doing under the hood and if it's considered "safe" based on historical data. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://cerbero-tools.gitbook.io/home/tools/eth-suite/contracts.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.