The short version
A block explorer is a record: it decodes and displays blocks, transactions, logs and verified contract source exactly as they happened. It doesn't have an opinion on whether a token is a rug, because that's not the job it was built for. ScanHood is a safety layer: it runs a real buy-then-sell simulation on a token before you touch it, checks whether its liquidity is actually locked, and scores its deployer against a database of known ruggers, then feeds that verdict into a scanner, a screener, a swap that blocks DANGER tokens outright, and a portfolio tracker.
Feature by feature
| Capability | Blockscout-style explorer | ScanHood |
|---|---|---|
| Raw blocks, transactions, logs | Yes | Yes (own /explorer) |
| Verified contract source | Yes | Links out to it |
| Token holder lists, transfers | Yes | Yes |
| Honeypot / buy-sell simulation | No | Yes, on every scan |
| LP-lock verification | No | Yes, checked on-chain |
| Deployer reputation / serial-rugger scoring | No | Yes |
| Live market data (price, mcap, liquidity) | No | Yes |
| Trending / new-launch screener | No | Yes (/dex, /launch) |
| Trade execution gated by a safety verdict | No | Yes (/swap blocks DANGER tokens) |
| Wallet portfolio + watchlist with live verdicts | No | Yes (/portfolio) |
| Public REST API for the above | Yes (chain data) | Yes (safety + market data, see /docs) |
Where each one actually wins
🔍 Explorer, strong at
- Decoding a specific transaction, byte for byte
- Reading a contract's verified source directly
- Tracing the full history of an address
- Auditing internal calls and raw event logs
🛡️ ScanHood, strong at
- Telling you if a token can actually be sold
- Flagging a deployer with a rug history, before launch
- Surfacing what's trending or newly launched, ranked
- Blocking a trade into a DANGER-rated token outright
Using them together
The two aren't competing for the same moment. In practice the useful flow runs through both, in this order:
Frequently asked
Is ScanHood a fork of Blockscout?
No. Blockscout is open-source block explorer software that many EVM chains deploy to show raw chain data, blocks, transactions, verified source, logs. ScanHood is a separate, purpose-built safety layer: honeypot simulation, LP-lock verification and deployer reputation scoring, plus a screener, swap, launchpad and portfolio tracker built on top of that safety engine.
Does ScanHood replace my block explorer?
Not for raw data lookups. Use a block explorer (ScanHood's own /explorer, or any Blockscout instance) to read a transaction, decode a log, or verify contract source. Use /scanner before you trade, to see whether a token can actually be sold, whether its liquidity is locked, and whether its deployer has a rug history.
Can a token look fine on Blockscout but still be a rug?
Yes. A block explorer shows you that a contract exists, is verified and has holders. It doesn't simulate a buy-then-sell round trip, so it can't tell you a token is a honeypot until someone actually gets stuck holding it. That's the specific gap ScanHood's scanner is built to close.
Is ScanHood's data available over an API, like an explorer's?
Yes, see /docs: scan, search, OHLCV and launch endpoints, plus an llms.txt and OpenAPI spec for agents. Free, rate-limited, no key required for read endpoints.