| Name | Related DEX | Address | Token Price (USD) |
|---|---|---|---|
| LBTC / WBTC 0.05% | uniswap_v3 | 0x8742...6ca9 | 63207.4647594271 |
| LBTC / WBTC 0.01% | uniswap_v3 | 0x0b59...6460 | 63136.3109834028 |
| LBTC / WBTC | fluid-ethereum | 0xe0cc...9e5f | 63234.6167268422 |
| LBTC / WBTC | curve | 0x2f3b...06f0 | 63132.8531101433 |
| LBTC / USDC 88% | uniswap-v4-ethereum | 0x23bf...b359 | 44747.1553450737 |
| LBTC / cbBTC | fluid-ethereum | 0xc8f9...bda4 | 63652.3996112386 |
| LBTC / WBTC 0.01% | supernova-cl | 0xa2e0...3bd2 | 65272.0823906449 |
| LBTC / USDC 0.3% | uniswap-v4-ethereum | 0x0ccd...7162 | 108339.238336196 |
| eBTC / LBTC / WBTC | curve | 0xabaf...9502 | 64527.9957975737 |
| LBTC / USDT 0.01% | uniswap-v4-ethereum | 0x550a...d3fa | 67569.1200643683 |
| eBTC / LBTC 0.02% | uniswap-v4-ethereum | 0xef0c...cbf4 | 62206.9841393064 |
| LBTC / USDT 0.3% | uniswap-v4-ethereum | 0x5af3...b383 | 45452.0633507591 |
| LBTC / WBTC 0.01% | uniswap-v4-ethereum | 0x4006...e8b2 | 61206.6789117309 |
| LBTC / WBTC 1% | pancakeswap-v3-ethereum | 0xd600...25f3 | 63037.6858537165 |
| LBTC / WBTC 1% | uniswap-v4-ethereum | 0x7130...5fae | 63166.5867671766 |
| LBTC / WBTC 0.01% | pancakeswap-v3-ethereum | 0xc6f2...eb98 | 82686.0311202395 |
| eBTC / LBTC 0.05% | uniswap_v3 | 0xf93b...a85f | 81205.0498204106 |
| LBTC / XAN 1% | uniswap-v4-ethereum | 0x4e38...e4ba | 119359.358330425 |
| inLBTCs / LBTC 0.1% | uniswap-v4-ethereum | 0x0ec7...2d7d | 93219.4103643421 |
| strBTC / cbBTC / LBTC | curve | 0x8c5a...9305 | 87043.8108041718 |
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.