Name | Related DEX | Address | Token Price (USD) |
---|---|---|---|
MFT / WETH | uniswap_v2 | 0x2084...7d3e | 0.00128352499873006 |
MFT / WETH 1% | uniswap_v3 | 0x387c...87c8 | 0.00474000932052238 |
MFT / DAI | uniswap_v2 | 0xe805...b2a9 | 0.00136928100451978 |
MFT / USDC 0.3% | uniswap_v3 | 0x2908...97f5 | 0.002707916177 |
USDC / MFT 1% | uniswap-v4-ethereum | 0x3580...4df4 | 0.002638883561 |
MFT / WETH 0.3% | uniswap_v3 | 0xfbba...fc13 | 0.006763065437 |
MFT / USDC 1% | uniswap_v3 | 0xbbb2...ff97 | 0.00481346937589370993000311194256 |
MFT / USDC | uniswap_v2 | 0xacb9...5001 | 0.0003064482689 |
Generally, a honeypot Detector operation consists of a computer, applications and data that simulate the behavior of a real system that would be attractive to attackers, such as a financial system, internet of things (IoT) devices, or a public utility or transportation network. It appears as part of a network but is actually isolated and closely monitored. Because there is no reason for legitimate users to access a honeypot, any attempts to communicate with it are considered hostile.