Etherscan tells you what happened on-chain. RektRadar tells you whether it is a scam. The two tools sit at different layers of the stack and they answer different questions, even though casual users sometimes treat them as substitutes.
This post lays out exactly what each does well, what it does not do at all, and how the two fit together. If you already use Etherscan and you wonder whether a dedicated scam detector adds anything, the short answer is yes. The long answer is below.
What Etherscan does well
Etherscan is the canonical block explorer for Ethereum mainnet. It has been the default reference since 2016 and almost every other tool in the ecosystem links back to it. Its strengths are clear:
- Verified source code. When a contract author publishes their Solidity source, Etherscan compiles it and matches the bytecode. You get a readable view of the contract instead of disassembled opcodes. This is the single most useful feature for any kind of manual review.
- Holder distribution. The Holders tab shows you who owns the token, sorted by balance, with percentage of supply. You can spot a single wallet holding 80% of the supply in two clicks.
- Transaction history. Every transfer, every contract call, every internal transaction is searchable and filterable. For forensic work after the fact, there is no faster way to retrace what a deployer did.
- Label cloud. Etherscan’s team and community label thousands of addresses: known exchanges, DEX routers, scam wallets, MEV bots, public figures. The labels are not exhaustive but they cover the common cases.
- Contract reads and writes. For any verified contract you can call view functions directly from the UI and write functions if you connect a wallet. This turns Etherscan into a minimal frontend for any deployed contract.
- Token approvals view. You can see every approval an address has granted and revoke them from the same UI. Critical for cleaning up after a bad signing.
For the boring, indispensable work of looking up a transaction or reading a contract, Etherscan is fine and probably always will be.
What Etherscan does not do
Etherscan is a block explorer, not a scam detector. The product was never built to answer “is this token safe to buy”. A few specific gaps follow from that:
- No honeypot test. Etherscan does not simulate a sell to check whether the contract reverts on non-owner transfers. You can read the source and try to spot the trap manually, but if the contract is unverified, you have only bytecode to work from.
- No deployer graph. Etherscan shows you the deployer wallet’s transaction history, but it does not cluster that wallet against other deployers, does not surface its funding chain, and does not flag it as a known scam factory even if it has shipped 30 honeypots in the last 60 days.
- No factory pattern detection. Some scam operations deploy through factory contracts that produce hundreds of near-identical tokens with rotating names. Etherscan shows each token in isolation. There is no view that says “this contract was deployed by the same factory as 47 other rugged tokens”.
- No real-time mempool watching. Etherscan only shows confirmed transactions. By the time a rug-pull liquidity removal lands in a block, retail has already lost the buy. Mempool monitoring catches the unconfirmed transaction 10 to 90 seconds earlier.
- No automated risk score. There is no 0-100 verdict, no flag list, no “this is probably a honeypot” banner. Anything you conclude about a contract’s safety is your own analysis from the raw data.
- No rug-pull alerts. You cannot subscribe to a deployer wallet and get pinged when it deploys a new contract or pulls liquidity. You have to check by hand, repeatedly.
These are not bugs. Etherscan does its job. The job is just not “decide whether a random token on Uniswap is a scam”.
What RektRadar does
RektRadar is a real-time scam detector built specifically for Ethereum tokens. The whole pipeline is pointed at one question: is this contract dangerous, and if so why. The angles we cover:
- Mempool monitoring. Two of our three Ethereum nodes are dedicated mempool shards. We see suspicious liquidity removals, sandwich-bot positioning, and rug-pull preparations seconds to minutes before they confirm.
- Deployer-pattern matching. Every deployer wallet we touch gets clustered against our database of known scam wallets, funders, and prolific deployers. If your token’s deployer shipped 14 brand-jacks in the last quarter, you see that on the report.
- Factory tagging. Contracts deployed through known scam factories get flagged regardless of name or branding. The factory address is what we trust, not the surface metadata.
- Automated risk score. Every contract gets a 0-100 score across 80+ flags: honeypot simulation, hidden mint, blacklist functions, owner privileges, LP lock status, holder concentration, deployer history, mempool behavior, and more. A non-developer can read the verdict in five seconds.
- Public datasets. Hub pages like /scam/PEPE, /scam/USDT, and /scam/XRP list every contract that has used a given ticker, sorted by risk. Useful for buyers who type a ticker into DEX search and want to see which version is the real one.
- API and shareable reports. Every scan produces a permanent URL. Send the link to a friend who is about to buy and they see the same verdict you saw.
The pipeline runs on three Ethereum nodes (one mainnet, two mempool shards), 18 microservices, and a Postgres that has indexed every contract we have ever analyzed. The detail of what we built and why is in Why we built RektRadar.
Side-by-side comparison
| Capability | Etherscan | RektRadar |
|---|---|---|
| Verified source code view | Yes (canonical) | Inherited from Etherscan |
| Holder distribution | Yes | Yes (with concentration flags) |
| Transaction history | Yes (canonical) | Aggregated, not raw |
| Deployer history | Per-wallet, manual | Clustered with risk tags |
| Deployer graph (funders, related deployers) | No | Yes |
| Factory pattern detection | No | Yes |
| Mempool monitoring | Pending pool view only | Dedicated shards, alerting |
| Honeypot simulation (sell test) | No | Yes |
| Automated 0-100 risk score | No | Yes (80+ flags) |
| Rug-pull alerts on watched wallets | No | Yes |
| Brand-jack ticker hub pages | No | Yes (200+ tickers) |
| Token approval revoke UI | Yes | No |
| Free tier | Yes (with rate limits) | Yes (free scans) |
| Public API | Yes (paid tiers) | Yes |
The pattern is consistent: Etherscan owns raw chain data and contract source. RektRadar owns the derived signals — clustering, scoring, mempool, alerts — that Etherscan does not produce.
When to use Etherscan only
If your question is “what does this contract actually do” and you read Solidity, Etherscan is the tool. The verified source view, the read/write tabs, and the transaction filters are unmatched. You do not need a scam detector to read code.
If your question is “where did this transaction come from” or “which addresses interacted with this contract”, Etherscan’s filters and labels are again the right starting point. Forensic work on a confirmed transaction lives there.
If you only need to revoke an approval, Etherscan’s revoke UI gets the job done.
When to use RektRadar only
If you are about to buy a token in the next sixty seconds and you do not read Solidity, you need an automated verdict, not a contract source view. Paste the address into app.rektradar.io. The scan completes in 8 to 25 seconds with a 0-100 score and the specific flags that triggered.
If you are searching by ticker and you know that brand-jacking is a problem (it is, see the top 10 most brand-jacked tickers on Ethereum), the hub pages on RektRadar are faster than reconciling Etherscan results by hand.
If you want to be alerted when a known scam deployer ships a new contract, Etherscan does not offer that. RektRadar does.
When to use both together
In practice, anyone doing serious work on Ethereum tokens uses both. The flow we see most often is:
- Spot the token. DEX screener, Telegram, Twitter, wherever.
- Run the address through RektRadar to get a fast verdict and a list of flags.
- If the verdict is borderline or the flag list is unfamiliar, open Etherscan to read the verified source and check the deployer’s recent transactions yourself.
- Make the decision based on both views.
The tools do not compete for the same step. RektRadar compresses the “is this safe” question into ten seconds. Etherscan supports the deeper read when the score does not give you full confidence on its own.
A concrete walkthrough: a fake $XRP contract
To make the comparison less abstract, take a contract from our $XRP scam tokens deep dive. Pick one of the fakes — 0xbd7b6961c2c1d808089d5349ce2b1b58e68d71ee. Here is what each tool tells you.
On Etherscan, you get the contract page. The token name is “XRP”, the supply is round, the holder count is small but plausible. If the source is verified, you can read the Solidity. If it is not, you see opcodes. The deployer wallet is linked at the top of the page; clicking through shows their other transactions in chronological order. There is no warning banner. There is no risk score. The page is neutral on the question of whether this contract is safe.
If you know what you are looking for, you can find the trap. The transfer function may have a check that reverts for non-owner sells. The owner may not be renounced. The LP token might still be in the deployer’s wallet. But Etherscan does not surface any of these as “this is suspicious”; it shows them as raw data and leaves the inference to you.
On RektRadar, the same address returns a score of 80/100 high-risk with the flags honeypot, sell_failed, creator_holds_all_lp listed at the top. The deployer is tagged as prolific_deployer because it has shipped many similar contracts. The page links to other contracts from the same deployer, several of which are also flagged. The verdict is in the first second. The supporting evidence is one click away.
The contracts are the same. The data is the same. The difference is whether the tool’s job is to surface the signal or just to render the chain.
What about the Etherscan token info page?
Etherscan does have a “token info” pop-up on token pages that surfaces some lightweight signals — known scam status if a community report has been filed, holder count, top holders, and basic supply information. This is useful and we do not want to undersell it. Two caveats:
First, the scam-status flag is a manual community-driven label. It catches well-known scams after they have been reported. It does not catch a contract deployed in the last two hours that has not yet been seen by the labelers.
Second, the token info page does not run a honeypot simulation, does not fetch the deployer cluster, and does not check the mempool. It is a static metadata enrichment, not a dynamic risk analysis. Etherscan never positioned it as a substitute for a dedicated detector and we agree with that framing.
What does not change between the two tools
Some things are the same regardless of which tool you use, and they are worth naming so the comparison stays honest.
The chain data is canonical. Both tools read from Ethereum mainnet. If a contract has 47 holders, both tools see 47 holders. The disagreement is never about what is on-chain; it is about which signals are surfaced and which are left implicit.
The verified source code, when it exists, is the same. RektRadar uses the same Etherscan-verified source we all do. We do not have a private compiler match. The Solidity you see is the Solidity Etherscan saw.
Confirmed transaction history is the same. We may aggregate it differently or surface it inside the deployer graph, but the underlying transactions came from the same blocks.
The places we add value are: real-time mempool (data Etherscan does not aggregate as a primary signal), deployer graph clustering (data we generate offline against our database), automated risk scoring (a derivation, not a primary data source), and brand-jack ticker hubs (an aggregation across our scan database). None of these compete with what Etherscan does best.
Honest verdict
Etherscan is the indispensable explorer. RektRadar is the runtime safety layer on top of the chain data Etherscan exposes. They are not substitutes, and any post that frames them as competitors is missing the point.
If you can only have one tool open while you trade, it should be RektRadar — the verdict latency and the flag detail are the difference between catching a rug pre-buy and reading the post-mortem. Etherscan is the reference you fall back to once you need to understand the why behind the verdict.
For the seven concrete checks you can run before any buy, see How to detect an Ethereum scam token. For the philosophy behind the project, Why we built RektRadar covers the original motivation.