Transparent analysis

MEV detection methodology

SandwichCheck reports observable transaction patterns. It separates what the chain proves from what must be inferred about intent or profitability.

Current decision process

  1. Locate

    Resolve a submitted transaction hash, or find recent supported swaps sent by a submitted wallet.

    Fetch the mined block and locate the victim’s transaction index.

  2. Classify

    Decode supported router calls to identify the target pool and swap direction.

    Search earlier and later transactions in the same block for the same pool.

  3. Grade

    Require a preceding swap in the victim’s direction and a following swap in the opposite direction, linked to the same surrounding sender.

    Return the candidate frontrun and backrun hashes as inspectable evidence.

Supported signals

Each signal carries a confidence level. The grade on a result comes from the strongest signal found.

High confidence
Linked sandwich structure and recognized liquidation calldata.
Medium confidence
Identical calldata sent to the same contract earlier in the block by a different sender.
Low confidence
An unlinked opposite-direction backrun or swap events across multiple pools.

Verdict meanings

Every result comes with a grade and the transactions behind it, so you can check our reasoning instead of taking it on trust.

High confidence
High-confidence MEV detected. The analyzer found a strong supported pattern, such as a linked sandwich.
Candidate
MEV-related activity found. One or more supported signals were found, but the result may require traces and profit accounting.
No pattern found
No supported MEV detected. No matching pattern was found within current coverage. This is not proof that the transaction experienced no MEV.
Not graded
Pending, reverted, not found, or unsupported. The transaction cannot yet be evaluated, did not execute successfully, is unavailable, or does not match a supported pattern.

Limitations

  • Protocols

    The live analyzer recognizes Uniswap v2/v3 swap events and known Balancer, 1inch, 0x, Odos, CoW Protocol, Aave V3, and KyberSwap entrypoints. Underlying pool and adapter attribution still requires traces.

  • Window

    Analysis is bounded to 12 transactions on either side of the selected transaction to control RPC cost.

  • Attribution

    Sophisticated searchers may use multiple addresses, private bundles, or intermediate contracts.

  • Profit

    Production attribution should additionally include traces, internal calls, token transfers, builder data, and net profit after gas and fees.

  • Wallets

    Wallet-wide lookup requires a separate indexed history provider.