Skip to main content

Use Cases

Practical workflows for detecting and investigating MEV activity using the Blockline API.

Detect & Investigate Sandwich Attacks

The most common workflow: scan your wallet for sandwich attacks, then drill into specific attackers.

The 3-Step Flow

1

Scan your wallet

Use check-wallet to find all sandwiched trades in the last 1–4 days.
2

Review results

Identify which attackers are targeting you and how often.
3

Investigate an attacker

Use check-attacker to get a full profile: which DEXes, validators, pools, and timing patterns.

Step 1: Scan your wallet

Submit your wallet address to find all DEX trades that were sandwiched.
This returns a jobId — poll /mev/job-status/:jobId until the job completes:
Key takeaway: Out of 823 transactions, 720 were DEX trades, and 267 were sandwiched — that’s 37% of all trades. The incidents array shows the attacker wallet DDm1Bc9... placed transactions both before (sandwich_frontrun) and after (sandwich_backrun) the victim’s trade in the same slot.
A poh_tick_offset of 0 means the attacker’s transaction was in the exact same PoH tick as the victim — this is intra-slot sandwich detection, unique to Blockline’s PoH-level timing data.

Step 2: Quick-check a specific transaction

Already know which transaction to check? Use the synchronous check-sandwich-fast endpoint for an instant result — no job polling needed.
Notice the attacker (DDm1Bc9...) sent multiple attempts — two frontrun and two backrun transactions. One of each failed (success: false), which is typical MEV bot behavior: they spam transactions to maximize their chance of landing.
slot_range: 0 means intra-slot only — the attacker’s transactions must be in the same slot as the victim. Use higher values (e.g., 1 or 5) to catch cross-slot sandwiches.

Step 3: Investigate the attacker

Now that you’ve identified DDm1Bc9KuXB7Q2UbxyMRLGmbcV2J93xmiWDPt7Edhqbs as a sandwich attacker, get their full profile.
The attacker profile reveals:
The by_validator field shows which block producers the attacker lands sandwiches through. A high concentration on Jito validators suggests the attacker uses Jito bundles to guarantee transaction ordering — a common MEV extraction technique on Solana.

Choosing the Right Endpoint


Front-Running Detection

Analyze transactions that occurred before yours in the same slot to detect potential front-running.

Speed Ranking

Compare transaction timing and PoH tick offsets to understand execution speed advantages.

Pattern Recognition

Identify recurring MEV patterns and bot behavior in specific markets.
More detailed guides for these use cases are coming soon.