Name | Related DEX | Address | Token Price (USD) |
---|---|---|---|
FIGHT / WETH | uniswap_v2 | 0x63a1...98f6 | 0.00056017740092726 |
FIGHT / USDT 40% | uniswap-v4-ethereum | 0x30f5...f1c8 | 0.0004256182861 |
FIGHT / ETH 3% | uniswap-v4-ethereum | 0x3d3e...01b7 | 0.0006683808941 |
FIGHT / WETH 1% | uniswap_v3 | 0x6de1...e542 | 0.0006618666512 |
FIGHT / WETH 0.3% | uniswap_v3 | 0x14e1...ef6a | 0.043546801029133 |
FIGHT / USDC 1% | uniswap_v3 | 0x5f6b...0550 | 0.0518158531113238 |
FIGHT / USDC 0.3% | uniswap_v3 | 0xd6c3...5d49 | 0.00969371525268852 |
FIGHT / KABOSU | uniswap_v2 | 0x1858...48c2 | 0.001034525233 |
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.