| Name | Related DEX | Address | Token Price (USD) |
|---|---|---|---|
| MUSE / WETH | uniswap_v2 | 0x20d2...bf43 | 0.601383214355954 |
| MUSE / ETH 1% | uniswap-v4-ethereum | 0xc36b...cefc | 0.598427782112825 |
| MUSE / WETH 1% | uniswap_v3 | 0xf5e4...ac71 | 0.5943469053 |
| MUSE / USDT 88% | uniswap-v4-ethereum | 0x857c...5d14 | 0.5493612329 |
| USDC / MUSE 88% | uniswap-v4-ethereum | 0x5912...939a | 0.5466667765 |
| CUDL / MUSE | uniswap_v2 | 0x9403...1215 | 0.6003506169 |
| MUSE / HYPE | uniswap_v2 | 0xe082...284c | 0.5507476342 |
| BPT / AUDIO / YGG / SAND / NFTX / MUSE / AXS / WETH 1% | balancer_ethereum | 0x344e...0df2 | 0.373092669390480115685175264236 |
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.