Sandwich attack checker FAQ
Clear answers about what the analyzer checks, what its verdicts mean, and where the evidence comes from.
Can a sandwich still be detected after the transaction is mined?
Yes. Pending transactions normally leave the mempool when included, but the mined block preserves transaction order. Receipts, logs, traces, and token flows can support post-trade analysis.
Can I search by wallet address?
Yes. The analyzer accepts a transaction hash or wallet address. Wallet analysis depends on the history exposed by the configured node and the swaps recognized by the current decoder.
Does “no targeting detected” prove the swap was safe?
No. It means the analyzer found no matching same-block sandwich pattern within its current scope. Other MEV strategies, unsupported protocols, or more complex attacker address patterns may not be detected.
Does the attacker’s transaction remain in the mempool?
Not after normal inclusion. Once mined, it becomes part of the canonical block and is removed from the pending pool. If it is replaced, dropped, or reorged, node behavior may differ.
Which networks are supported?
Ethereum Mainnet and Sepolia are supported when their read-only RPC endpoints are configured. The detector recognizes mined Uniswap v2 and v3 swap events.
Is a submitted identifier indexed by search engines?
Analyzer URLs containing query parameters are marked noindex. The app sends the identifier to the configured backend for analysis; deployment operators remain responsible for logs, retention, and privacy policies.