| Name | Related DEX | Address | Token Price (USD) |
|---|---|---|---|
| HONK / WETH | uniswap_v2 | 0x4b74...2279 | 0.0000000007518367756 |
| HONK / SLACK | uniswap_v2 | 0x3e38...ebcd | 0.0000000007487647238 |
| TrumpBucks / HONK 1% | uniswap-v4-ethereum | 0xa4fd...89c5 | 0.000000000746503580730117 |
| HONK / ETH 1% | uniswap-v4-ethereum | 0x20b4...85e8 | 0.0000000007495470661 |
| LANDWU / HONK | uniswap_v2 | 0xbe56...6ce4 | 0.000000000724433972577217 |
| TrumpBucks / HONK 1% | uniswap_v3 | 0xd34a...843e | 0.000000004087735161 |
| KEK / HONK | uniswap_v2 | 0x6475...8893 | 0.00000000790870348242148 |
| n / HONK | uniswap_v2 | 0xaa8c...d4d3 | 0.00000000963334139088864 |
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.