Name | Related DEX | Address | Token Price (USD) |
---|---|---|---|
BLZ / USDC | uniswap_v2 | 0x5fa9...50df | 0.0365701674592784 |
BLZ / WETH | uniswap_v2 | 0xcf42...491e | 0.0366586605436569 |
BLZ / WBTC | uniswap_v2 | 0xd65b...0a92 | 0.037839815411628 |
BLZ / USDC 1% | uniswap_v3 | 0xa5e5...34ad | 0.033818653238332 |
BLZ / ABDS 1% | pancakeswap-v3-ethereum | 0x2bf7...f1a0 | 0.03385051885 |
BLZ / WETH 1% | uniswap_v3 | 0x1d6d...d73e | 0.000544824429843011275856599854184326313451000133549590558 |
BLZ / KABOSU | uniswap_v2 | 0x28c7...7065 | 0.04167090733 |
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.