| Name | Related DEX | Address | Token Price (USD) |
|---|---|---|---|
| ynETHx / WETH | curve | 0xd65e...6f8f | 3121.5251596342 |
| ynETH / ynETHx | curve | 0xd04e...a63e | 3121.39904646859 |
| ynETHx / ynETH | curve | 0xeada...50cb | 3426.905570950107148721255509543260081243872751188188158542308017 |
| ynETHx / YND | curve | 0x8e6f...7d48 | 3261.75493014474 |
| xETH / ynETHx | curve | 0x0589...35e7 | 3176.8021714089 |
| ynETHx / ETH 90% | uniswap-v4-ethereum | 0x8eee...4989 | 407.5933008976 |
| ynETHx / USDT 88% | uniswap-v4-ethereum | 0x00b0...f63e | 530.6127438146 |
| ynETHx / OETH | curve | 0xbeb1...3157 | 2697.0419686119 |
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.