| Name | Related DEX | Address | Token Price (USD) |
|---|---|---|---|
| DF / WETH | uniswap_v2 | 0x2328...1788 | 0.0003331858887 |
| USDx / DF | uniswap_v2 | 0xfe73...b3af | 0.000332375861143858 |
| USX / DF | uniswap_v2 | 0xdae6...ea46 | 0.000335600963211782 |
| DF / USDC 97.36% | uniswap-v4-ethereum | 0x6cbf...bbfb | 0.0003095772976 |
| DF / USDC 82.5% | uniswap-v4-ethereum | 0xe483...8bc2 | 0.001309130029 |
| UTS / DF | uniswap_v2 | 0xa0e7...508d | 0.0003370855723 |
| DF / USDC 88% | uniswap-v4-ethereum | 0x1f31...a4cb | 0.0003086111467 |
| DF / WETH | sushiswap | 0xfe66...0c18 | 0.0002148381465 |
| DF / KABOSU | uniswap_v2 | 0xdeae...42bc | 0.0112265875 |
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.