Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Dive into transactions and Act Wisely
Phalcon Explorer is a powerful transaction explorer designed for the DeFi community. It provides comprehensive data on invocation flow, source code, balance changes, transaction fund flows, gas profiler, and state changes. It also supports transaction debugging and transaction simulation. This tool aims to help developers, security researchers, and traders intuitively understand transactions.
We value your input and would greatly appreciate any feedback or suggestions you may have.
Here is a list of blogs on how to use Phalcon Explorer
Our Anti-MEV RPC on BSC supports the method eth_sendBundleto send multiple private transactions in a bundle.
RPC Endpoint: https://bsc.rpc.blocksec.com
POST /
Send private transactions in a bundle
txs
Mandatory
array[hex]
["0x…35", "0x…4e"]
List of signed raw transactions.
maxBlockNumber
Optional
uint64
47793530
Maximum block number for the bundle's validity. Default is current block number + 100.
revertingTxHashes
Optional
array[hash]
["0x…2c", "0x…3d"]
List of transaction hashes allowed for revert.
One example of the detailed request.
Ensuring a Secure and Seamless Web3 World
BlockSec is a full-stack blockchain security service provider. It was founded by top-notch security researchers and experienced experts from academia and industry.
BlockSec has published multiple blockchain security papers in prestigious conferences, reported several zero-day attacks of DeFi applications, blocked multiple hacks to rescue more than 20 million dollars, and secured billions of cryptocurrencies.
We provide both security services and products before and after the protocol launch.
: In-depth smart contract and EVM chain audits
Thorough audits covering technical, business, and financial aspects
Professional report with actionable solutions for identified issues
Cover Solidity, Rust (Near and Solana), and Go language (Cosmos)
BlockSec Phalcon: A platform to monitor and Block Hacks
Block Phalcon helps users, protocol operators, traders, and everyone to perceive suspicious transactions, get instant alerts, and take automatic actions. Its battle-tested capability has been proven by successfully thwarting 20+ real-world hacks and rescuing over $14,000,000 worth of assets.
Phalcon Explorer: Dive deeply into transactions to act wisely
MetaSuites (previously MetaDock): Builders' Swiss Army Knife
MetaSleuth: A crypto tracking and investigation platform
Email: contact@blocksec.com
BlockSec: @BlockSecTeam
BlockSec Phalcon: @Phalcon_xyz
MetaSuites (Prev. MetaDock): @MetaDockTeam
MetaSleuth: @MetaSleuth
Telegram Group
Audit and Phalcon-related: https://t.me/BlockSecTeam
Scam, phishing, and crypto tracking: https://t.me/MetaSleuthTeam
The "sandwich attack" is one of the most common frontrunning methods in the DeFi space, where attackers place two transactions around a trader's swap order on a DEX, aiming to manipulate asset prices through this sandwiching approach, causing the trader to incur asset losses.
To address this, BlockSec has launched an MEV protection RPC, safeguarding users' DeFi journey.
Users need to add the corresponding RPC endpoints into their wallets to use these RPC endpoints. In the following, we will show the steps for some popular wallets.
Step 1: click on the top left to show the networks.
Step 2: Edit the network
Step 3: Click to add the RPC URL
Input https://bsc.rpc.blocksec.comfor BSC (or https://eth.rpc.blocksec.comfor Ethereum).
Ensure that the default RPC URL is the one we just set.
A Platform to Monitor and Block Hacks
is a new paradigm for securing protocols. It helps protocol detect hacks, operational, interaction and financial risks, get instant alerts, and take automatic action to prevent threats before they do any damage.
Its battle-tested capability has been proven by successfully thwarting 20+ real-world hacks and rescuing over $20,000,000 worth of asset.
Highlights of BlockSec Phalcon
Get early access to precise attack intelligence
Automated attack blocking with Customized Actions
No-code, flexible monitoring rules configuration
Meet both security and operational monitoring requirements
You can book a demo to talk with our technical support engineers before subscribing to Phalcon.
The detailed user manual of Phalcon can be accessed after subscribing to Phalcon.
The protocol operator can use Phalcon to monitor attacks on its protocol (smart contracts) and configure Phalcon to automatically pause the protocol when an attack is detected in the mempool or on the blockchain to prevent further losses.
Also, the protocol operator can use Phalcon to monitor sensitive operations related to its protocol, including updating critical configuration, changing admin roles, adding new owners to critical multisig wallets, withdrawing funds from the protocol by admins, and others. Awareness of such sensitive operations (can take corrective actions) is critical to maintaining the protocol's security since inside attackers (or private key leakage) can lead to significant loss to the protocol.
LPs are the people who deposit (or stake) many assets into some protocols. When a protocol is hacked, the LP's assets will be drained (not the protocols). Using Phalcon, LPs can get notifications when their investment protocols are hacked and automatically withdraw funds before others (or other strategies) to reduce loss.
L2 chain operators can collaborate with BlockSec to support Phalcon in its L2 chains. This can help secure the top protocols on the L2 chains, which uphold a thriving ecosystem. Besides, L2 chains can integrate Phalcon deeply inside the chain (e.g., the sequencer) to create an even more secure ecosystem from the root.
Centralized exchanges (CEX) can automatically use Phalcon to delist tokens affected by hacks. Otherwise, the valueless tokens can be sold in exchanges, which causes loss.
How to use Phalcon Explorer
Link: https://app.blocksec.com/explorer
Input a transaction hash into the search box to start using Phalcon Explorer. Also, the history of the transactions searched is shown below.
In the following, we will use this transaction to show how to use Phalcon Explorer.
Input the transaction hash and click enter to show the main GUI of Phalcon Explorer.
The main GUI shows the following information for a transaction.
The Basic Info displays the basic information of the transaction, including the execution status (Status), the sender (Sender), and the recipient (Receiver).
The internal transaction count indicates the number of internal transactions, which can be used to determine the transaction's complexity. The higher the value, the more complex the transaction.
The [Simulator] button in the top right corner allows you to quickly simulate the results of the current transaction at different Block Number [BlockNum] and position [position in the block] (The transaction simulation will be explained in this Section).
The Fund Flow module illustrates the flow of tokens involved in the transaction as a directed graph. Different nodes represent different addresses, and a different background color distinguishes nodes representing the sender or recipient of a transaction.
The directed edge and the information on the edge show the transfer direction, the token, and the number of tokens transferred.
Different serial numbers on the edges are used to distinguish the chronological order of the token transfers.
Edges of the same color identify transfers of the same token,
The same directional flow of the same token between two addresses is merged to simplify the transaction's fund flow map while preserving the characteristics of the token transfer.
The Balance Changes shows the accounts that have a change in the token balance after the transaction is executed.
The first column lists the addresses with a net inflow or outflow of tokens.
The second column lists the token information, including the names of the token that flows in or out of the address.
The third column shows the change in balance, i.e., the token inflow or outflow amount.
The last column shows the value in USD of the number of tokens flowing in or out of each account when the transaction occurred.
The gas profiler uses the Flame Graph to show the gas used in each function invocation.
Each line in the graph denotes the gas used in each function. Click the function name to show the detailed gas used inside that function.
The state changes show the changes in the storage in this transaction.
This feature is handy when you need an overview of the change to some critical states. For instance, in the recent Tornado Cash Dao attack incident, using this feature can quickly detect malicious proposals to change the locked Balance in Governance for 100 addresses directly.
Note that Phalcon Explorer supports complicated storage layouts. See this blog for more information.
Invocation Flow displays the sequence of function calls in a transaction as a tree structure.
Each node represents a function call or event trigger and includes information such as call stack depth, call type, and call parameters. A search box and a drop-down selection box for call type and expansion are provided at the top of the module to assist users in interpreting the transaction execution flow.
Users can search for and filter desired call flow information by entering an address, function signature, or function selector in the search box.
Static Call: Whether the static call is shown in the flow.
Gas Used: Whether the gas used in each function call is shown.
Expand: How many levels in the invocation flow are to be shown? The following shows the invocation flow, which only shows two levels.
Phalcon Explorer supports features to facilitate the analysis.
The address, function, and event can be highlighted with a custom background color during the analysis.
The address, function, and event can be set with custom labels.
For the calldata of a contract, a custom function signature can be provided to decode the calldata.
The line number is shown in the invocation flow, which helps to locate a particular function call inside the flow quickly. For instance, if you find that the root cause of the exploit is in line N, you can click this line. The URL shown will include this line number. You can directly share the URL with your friends or on Twitter. Others who click the same URL (with the line number) will directly go through that line.
For instance, this link will directly navigate you to line 1250 in the invocation flow.
Phalcon Explorer Debugger
There are two different ways to enter the debug mode: from a specific line in the invocation flow view or by clicking the Debug button.
Another way to enter the debug mode is by clicking the Debug button in the upper right corner.
After entering the Debug mode, we can see the following screen.
This screen has five panels, which are as follows.
Call Trace Panel: Showing the trace of external calls and events.
Source Code Panel: Providing the contract's source code and the current line (highlighted) referring to the call site of a function.
Debug Console: a call-level single-step debug console.
Debug Trace Panel: Showing the call stack of the current contract with a combination of internal and external calls.
Parameters & Return Values Panel: Showing call parameters and return values.
Sometimes, you may notice that the source code panel does not show the code. This is because the panel shows the function's call site by default. The reason is that the hacking contract is not unverified (not open-sourced), so the source code cannot be shown.
The eDai contract is verified so we can Step In to see the specific implementation of donateToReserves(). After clicking Step In, the current line becomes the call site inside the eDai contract. It’s a proxy contract, and the code is shown below.
After Step In again, we can finally see the concrete implementation of donateToReserves().
The debug console helps understand the detailed call trace, including the internal function call (The Jump at the first of a line indicates that this is an internal call). Note that the Call Trace Panel does not have an internal call trace.
To traverse between the detailed execution, Phalcon provides four buttons on the Debug Console, and Next and Previous have slightly different logic under the two colors.
Next (Red Button): Go to the next call site in the whole call trace.
Next (Blue Button): Go to the next call site of the current function.
Previous(Red Button): Go to the previous call site in the whole call trace.
Previous(Blue Button): Go to the previous call site of the current function.
Step In: Go to the callee function.
Step Out: Return to the call site of the current function.
For instance, we can click the Next button to analyze the implementation of donateToReserves(). We can find that the hacker donated 100 million eDAI, making the eDAI less than the dDAI and eligible for liquidation. Therefore, the root cause is that donateToReserves() lacks of liquidity check for eligible liquidation, and the exploiter liquidated himself/herself and took out 38 million eDAI.
In summary, the typical workflow of using Phalcon Explorer Debugger to analyze a hack transaction follows.
Find the possible issue in Invocation Flow and start debugging from there.
Debug the source code, check the parameters, and return values of internal calls.
Share your analysis with team members (or public readers) for collaboration.
Phalcon Debug has many features to help you improve efficiency.
The Call Trace View can show the full parameters by turning on the parameters switch on the left top panel.
For external calls, click "Rawdata" can see the raw call parameters.
MetaSleuth is a crypto tracking and investigation platform. It can help monitor market movements, track fund flow of criminal activities, and DYOR to avoid scams.
Tips: Click the button on the top right to enter the full-screen mode of Phalcon Explorer.
Phalcon Explorer supports transaction debugging, a powerful feature that can significantly improve the analysis efficiency of complex transactions. In the following, we will illustrate this feature using the transaction of the exploitation of
Click .
Tx Hash:
The Invocation Flow in Phalcon provides a view that lets users take a complete picture of the hack transaction and identify possible exploitation locations. This is useful when hundreds of external calls and events may exist .
In the case of the Euler protocol exploitation, the hack transaction consists of many steps, including borrowing Flashloan from Aave, depositing Dai into the Euler protocol, etc. But in one of the steps, the exploiter called donateToReserves() to "donate" a massive fund to the Euler protocol, which warrants our vigilance. In this case, we can directly debug the transaction from this step by clicking the debug icon.
A transaction's debug can be shared directly via , which contains the trace’s row number. When others open the link, the same debug view will be shown. This is useful when you want to share the analysis result with others. Team members can use this to collaborate, analyze, and discuss together!
Everyone can become a sleuth in the crypto world and DYOR!
Visit -> for the full documents
Phalcon simulator allows a user to simulate a transaction at an arbitrary position of an arbitrary block. The simulated transaction can be viewed in Phalcon Explorer and shared with others.
This feature can be used in multiple scenarios.
Users: Understand the transaction before signing it
Developers: Debug a transaction
Security researchers: Simulate and debug an attack transaction
The simulator can be launched inside a detailed transaction.
Network: Select the network. Ethereum, BSC, Arbitrum, Optimism, Avalanche, and Polygon are currently supported.
Sender: The sender of the transaction (the from address)
Receiver: The target of this transaction (the to address)
Calldata: the detailed call data of this transaction. To facilitate the construction of the calldata, the call data can be specified using the contract ABI.
Value: the value of this transaction.
Gas Limit: The gas limit.
Gas Price: The gas price.
Use Pending Block: Whether the simulation occurs on the latest block or an old block specified in the Block Number. The default value is False.
Block Number: The block number where the transaction simulates.
Position in Block: The position inside the block.
When launching inside the transaction page, the transaction data is automatically fed into the simulator (and can be changed) for a quick simulation. This is useful when you just want to slightly change the data of an existing transaction, e.g., changing the position inside the block.
In the following, we will use some examples to illustrate this feature.
We can simulate a transaction to send 200 Ether to an address, e.g., from to vitalik.eth 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045to0xdeadbeef40e59eb8582ff949afb313e09c5815c9.
The simulated transaction can be viewed in Phalcon Explorer. The link to this simulated transaction can be shared with friends (the link is valid 48 hours after sharing).
When the Receiver is a contract, our system will get the ABI of the contract if it's verified and show the list of methods. Users can select a method to invoke in the transaction. For instance, the contract is USDC contract, and the method transfer is invoked to send USDC from the sender to the to value of the invocation.
If the contract is not verified, a Local ABI can be uploaded. Of course, a raw calldata can also be used.
MetaSuites (Prev. MetaDock) allows users to get a crypto address's fund flow map quickly. Users can analyze high-value correlated addresses and substantial fund flows without entangling complex raw transaction data.
🙌 If you need a comprehensive fund flow analysis for a couple of addresses, try the enhanced version MetaSleuth!
The fund flow map presents the most significant transactions and addresses for analysis, rather than every transaction. To access the fund flow map, you should locate the button on the address page.
The fund flow map may NOT show every transaction when addresses engage in numerous interactions. This is to maintain clarity and focus on the most relevant data for analysis. Transactions are merged on the fund flow map to provide a more streamlined view. For example, if address A sends 100 Token A to address B and then another 200 Token A to address B in two separate transactions at times A and B, the fund flow map will consolidate these into one transaction. It will display a single transfer of 300 Token A from address A to address B, with the timestamp from the first transaction, time A, on the chart.
For example, related addresses are shown in the fund flow map of Alameda Research, and some cross-chain transactions are also included. You can filter interested addresses and tokens (① on the following figure) by clicking and choosing on the top right corner, then get a streamlined chart like this:
Moreover, after the analysis, you can click the download icon(② in Fig.2 ) to export the chart as an SVG/PNG file and share it with others.
If you need further analysis, try the enhanced version of the fund flow map, MetaSleuth!
Steps to be taken for phishing attack victims
Please read carefully to understand actions that need to be performed to prevent further loss.
First, identify the cause and take appropriate measures to prevent further losses.
Second, attempt to recover the losses through tracking and investigation. It is important to note that recovering losses often requires significant time and effort (and it's nearly impossible to recover funds in most cases), so it is advisable to prioritize minimizing further damage promptly.
Third, read this document to become aware of phishing attacks and avoid becoming a victim of phishing.
If it is a case of private key compromise, it is recommended to immediately transfer the remaining assets from that address to a secure wallet on all relevant blockchains.
If your passphrase has been leaked, use a new passphrase to generate new addresses and transfer all remaining assets in the addresses generated by the leaked passphrase to new ones.
If it is a phishing incident, use Approval Diagnosis to revoke unnecessary approvals immediately to prevent further loss (very important!!!). Then, use MetaSleuth to track the fund flow and monitor the stolen funds if needed. Report to law enforcement and corresponding crypto exchanges.
Recovering stolen funds is generally difficult in most cases. Here are some suggestions:
If you have suffered significant losses, file a report with your local law enforcement agency. You can provide them with a phishing report or fund flow chart generated by MetaSleuth to help them understand the situation you have encountered.
If you urgently need to recover stolen funds, consider seeking assistance from professional investigation agencies or firms specializing in asset recovery.
DO NOT give sensitive information like your passphrase to anyone claiming they can recover your lost funds. DO NOT trust anyone who claims to represent BlockSec to recover your loss.
See our Twitter thread. https://twitter.com/MetaSleuth/status/1656144511934791680
MetaSleuth primarily assists you in two ways.
Firstly, you can use MetaSleuth to track stolen funds. If you discover that the stolen funds have entered centralized exchanges or flash exchanges, you can seek assistance from these platforms and gather evidence (usually with the help of law enforcement) to further the investigation.
Secondly, you can utilize MetaSleuth's monitoring feature to continuously monitor the stolen funds, enabling you to stay informed about the movement of funds and follow up on any leads.
Here are some contact information for exchanges (updating):
Bitfinex: Bitfinex Law Enforcement Requests Policy
Fixedfloat: info@fixedfloat.com
ChangeNow: compliance@changenow.io
StealthEX: support@stealthex.io
This page shows the APIs supported by Phalcon Explorer
Phalcon Explorer supports APIs that can be integrated into the user's internal system to understand a transaction better.
The Access Key is needed to access the API. Please contact us (contact@blocksec.com) for the Access Key.
MetaSuites (Prev. MetaDock) offers concise and informative explanations for most transactions displayed on the Transaction Details page of Etherscan.
These explanations encompass the main actions taken and provide essential security-related information. This intelligent service, powered by GPT, serves as a valuable reference for on-chain analysis, providing insightful explanations for most transactions and enhancing your understanding of the blockchain ecosystem.
Users can add their local labels to addresses on supported Blockchain browsers. These labels are stored in users' local storage. These labels can be used in the Phalcon Explorer in the same browser when the option is enabled.
MetaDock has another feature (It's turned off by default; you can turn it on in the settings panel) that shows the timestamp on the blockchain explorers using your local time zone rather than UTC.
If you want to explore the portfolio of an address, you can click the DeBank button near the Fund Flow button.
MetaSuites (Prev. MetaDock) provides users with an all-in-one dock to search for ENS, address, transaction hash, and selector (function signature).
ENS: MetaSuites automatically resolves it and turns to the Etherscan page of the corresponding address.
Address: it goes to the Blockscan page of this address that lists multi-chain links.
Transaction hash: it redirects to the transaction page of this hash.
MetaSuites (Prev. MetaDock) allows users to launch blockchain explorers quickly. Each icon leads you to the corresponding blockchain browser.
Pin the MetaSuites (Prev. MetaDock) extension for more convenience.
See for more information on avoiding being a phishing victim.
Try these transactions: , , , .
See:
MetaSuites (Prev. MetaDock) lets users download the current page's data as a JSON/CSV file. For example, the user can download the latest 25 transactions on this .
MetaSuites (Prev. MetaDock) helps all blockchain explorers add copy icons in some places to facilitate crypto users in conducting their own investigations and research. Try these pages:
Function selector: it utilizes to retrieve the function signature.
Dive into our collection of hack incidents driven by vulnerability exploits, uncover their underlying causes, and explore PoC codes. This is an essential reference to bolster your defenses against hackers!
The attack incidents causing losses exceeding $100K will be documented.
MetaSuites (previously MetaDock) is the Builders' Swiss Army Knife. It enhances experiences by integrating innovative features and connecting 30+ useful tools to blockchain explorers and dApps.
MetaSuites supports Chrome, Edge, Firefox, Safari, and Brave browsers.
Chrome and Edge users, please go to the Chrome Web Store to install MetaSuites. Other users can go to our landing page to get the installation instructions. Pin to Chrome to have a better experience.
Please support us to help us do better. Our wallet address is: 0x1220D3c0d62929DD970C411413FC854f7FeD00C6
and more
Please let us know if you have any questions about us and our products.
contact@blocksec.com
Telegram Group
Audit and Phalcon-related
Scam, phishing and crypto tracking
MetaSuites (Prev. MetaDock) identifies deposit addresses of CEXs, scammer and hacker addresses, and other addresses we collected and verified (especially those not tagged by the blockchain explorers). It helps users better understand the participants of transactions and track the flow of funds.
MetaSuites identifies several addresses on BTC.com as Binance Wallets. This makes the identification of CEX transfers easier.
For proxy contracts, MetaSuites gives you a hook to their implementation contracts in the label, which means you can click on the latter half of the label and directly turn to the implementation contract!
Note that MetaSuites does not collect and upload users' private tags.
MetaSuites provides the address compliance score to help estimate the likelihood of an address associated with illegal activities. Specifically, an address will fall into one of the five categories:
No risk: almost impossible to be related to illegal activities;
Low risk: the low possibility of being related to illegal activities;
Medium risk: the medium probability of being related to illegal activities;
High risk: high likelihood of being related to illegal activities;
Critical risk: those who are involved in illicit activities.
The compliance scores are provided for reference only and do not constitute any investment advice. Learn more about the methodology to calculate the risk scores.
Roam with MetaSuites!
BlockSec:
BlockSec Phalcon:
MetaDock:
MetaSleuth:
We offer Address Label and Compliance APIs. Click for more information.
Try this
Try these addresses:
Try this .
MetaSuites (Prev. MetaDock) enhanced a token approvals management tool by Etherscan that can help you identify and avoid risky approvals to phishing addresses or vulnerable contracts.
The approval mechanism in token transactions allows users to grant permission to other entities, such as smart contracts or other users, to spend their tokens on their behalf. For example, a user can approve a smart contract to use their USDC tokens, enabling the smart contract to perform operations like swapping USDC for other tokens without requiring further confirmation from the user. Once the tokens are approved for use by the smart contract, no additional signed messages are needed from the token owner for the smart contract to execute transactions with those tokens. This streamlines the transaction process by reducing the need for multiple confirmations.
However, the approval can be risky if the spender is a phishing address or a spender is a vulnerable contract. In both cases, the user's tokens can be stolen.
MetaSuites flags suspicious approvals to vulnerable contracts and EOAs (phishing accounts, unsafe accounts, etc.) Users can review the approvals here and revoke all risky approvals immediately to prevent further loss.
After installing the MetaSuites extension, the Approval Diagnosis button will be shown on the address page of the Etherscan.
After clicking the button, the detailed approval results will be shown. Risky approval will be displayed in red with notes!
We can see the approval of the phishing address. Unfortunately, the user did not notice this approval, and the attacker transferred 70 WBTC from this address (see the following figure).
If there is any risky approval, the user needs to remove the approval immediately. Just connect to the Web3 wallet and revoke all approvals flagged by MetaSuites.
Risky approval has been a significant threat to users, and MetaSuites helps users know of their risky approval. To stay safe, don't forget to make an approved diagnosis regularly.
While the blockchain is inherently immutable and transparent, obtaining the actual state of complete contract variables remains challenging, even for developers. MetaSuites enhances the functionality of the Reading Contract Tab on blockchain explorers by enabling the query of private variables.
For example, there is a private mapping called `_holderTokens` in the BAYC contract (0xbc4ca0...a936f13d), which stores the IDs of BAYC tokens held by each address. Previously, accessing this information on blockchain explorers like Etherscan was not possible. However, with MetaSuites, you can effortlessly query and retrieve such data in the appropriate location provided.
Try this contract.
Variables within a contract are subject to frequent changes as the blockchain progresses. While some variables remain immutable and constant, others are often updated, creating a complex landscape for developers and onchain detectives tracing their evolution.
MetaSuites offers a solution by facilitating log queries for a specific variable within a designated time frame. This can be defined by either timestamps or block heights. The system conveniently presents the time of the update, the new value after update, and the transaction hash, all in a versatile table. Furthermore, MetaSuites provides an option to export these logs into a CSV file, allowing for deeper investigation.
Please note that you can adjust the time range from the top right corner of the interface. The system intelligently limits the scope to a feasible time period - from the contract's deployment to the present moment. Given the intricacy of some variables, the list is capped at 300 records. For more focused results, consider narrowing down the time range.
Try this contract.
MetaSuites allows users to easily download verified contracts' source code and ABI files. It is pretty helpful for downloading contracts with multiple files. For a proxy contract, it will download the implementation contract simultaneously.
Try this contract.
If you want to view the project's source code directly on your browser in the VSCode style, just click View in DethCode.
There are numerous proxy contracts that can be upgraded when necessary, but they are also susceptible to exploitation by scammers. For developers and security researchers, it is highly beneficial to swiftly review the proxy upgrade log on the contract page. MetaSuites has integrated Cergyk's upgrade hub, and you can simply click on "Proxy Upgrade Log" to access a comprehensive log of typical proxy contracts.
Try this contract.
MetaSuites allows users to easily interact with popular developer-friendly tools such as Dedaub, Phalcon, Tenderly, Forta, etc.
If you meet an unverified contract like this contract, you can push the button Decomplile in Dedaub or Decompile in ethervm.io to get a better understanding of the contract.
MetaSuites intelligently presents the funding source of contract deployment to users, offering great assistance in executing compliance-related investigations. Try this address.
MetaSuites provides a more comprehensive function signature library to complement the *scan's signature parsing.
For example, MetaSuites replaces the function signature0x13d79a0b with settle， which makes more sense for users.
If you want to dive deeply into a transaction, MetaSuites assists you with multiple shortcuts to popular transaction browsers.
Phalcon provides many innovative features, such as invocation flow, balance changes, and transaction simulations.
Transaction Tracer and Tenderly are also very useful and popular among crypto users. Top EVM-compatible blockchains are supported.
Try this transaction.
If you are an MEV searcher, you may be interested in the bundles in the blocks, and you can utilize Flashbots Explorer near the block height.
Try this block.
Forta comprises a decentralized network of independent bots that scan all transactions and block-by-block state changes for threats and anomalies. MetaSuites is strengthened by the detection support of Forta, displaying additional labels and flagging suspicious transactions.
_holderTokens of the BAYC contract is accessible via MetaSuites.
