| Name | Related DEX | Address | Token Price (USD) |
|---|---|---|---|
| PUNKS / ETH | uniswap-v4-ethereum | 0x7207...596d | 12.2256369692 |
| PUNKS / USDC 14.99% | uniswap-v4-ethereum | 0x4dda...9d60 | 12.7296336209 |
| PUNKS / USDC 88% | uniswap-v4-ethereum | 0x4d14...a078 | 92.034215452 |
| PUNKS / ETH 15% | uniswap-v4-ethereum | 0x0abd...8332 | 440.5709503329 |
| PUNKS / USDC 87% | uniswap-v4-ethereum | 0xfd1b...75d8 | 64.9990250806 |
| PUNKS / ETH 12% | uniswap-v4-ethereum | 0xcc9e...c6b6 | 331.803353049 |
| PUNKS / ETH 14% | uniswap-v4-ethereum | 0x304b...79a8 | 547.3691021039 |
| PUNKS / ETH 10% | uniswap-v4-ethereum | 0xffe1...d92c | 415.2579240623 |
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.