| Name | Related DEX | Address | Token Price (USD) |
|---|---|---|---|
| UN5 / WETH 0.3% | uniswap_v3 | 0x411b...01fe | 0.0001144766893 |
| UN5 / UNI 0.3% | uniswap-v4-ethereum | 0x01a8...fd7e | 0.0001290790069 |
| UN5 / USDC 0.3% | uniswap-v4-ethereum | 0x90b1...fe42 | 0.000123069091 |
| UN5 / USDT 0.3% | uniswap-v4-ethereum | 0x50fa...4c7b | 0.0001218849782 |
| UN5 / WBTC 0.3% | uniswap-v4-ethereum | 0xb6f6...0b10 | 0.0001677083665 |
| UN5 / ETH 0.3% | uniswap-v4-ethereum | 0xf494...1168 | 0.0001145277481 |
| UN5 / USDT | uniswap_v2 | 0xeaba...a70f | 0.0001397765035 |
| UN5 / WETH | uniswap_v2 | 0x8313...9dde | 0.0002305527896 |
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.