XRPL DEX / AMM

Front-Run Monitor

Checking ledger...
Advanced ledger override
Candidate Alerts 0
Same Ledger 0
XRP Pairs 0
Attacker Profit XRP 0
Victim Loss XRP 0

Estimated Victims

No scan yet
Score Pair Victim Attacker Profit XRP Loss XRP Ledger Signal
Run a scan to populate candidates.

How to use

Front-Run Monitor Guide

What this tool does

This dashboard scans XRPL DEX and AMM exchange trades for probable sandwich / front-run patterns: an attacker trade, a victim trade on the same pair and side, then the attacker's opposite-side exit. Matches are scored as candidates — not proven theft.

Quick start

  1. Pick a time range with the 1d / 7d / 30d / 90d pills or set From and To.
  2. Adjust scan settings (pairs, filters) if needed.
  3. Click Run Scan. Requests run in your browser against the free XRPLData API.
  4. Review ranked candidates in the table; click a row for front-run, victim, and back-run details.

Scan settings

From / To
Calendar range for the scan. Converted to ledger indexes via GET /ledgers/ledger_index?date=.... Exchange trades are fetched for this exact window.
Quick ranges (1d, 7d, 30d, 90d)
Presets that set From/To relative to the latest ledger close time. Long ranges use a valid API ticker window (e.g. 90d scan uses a 13w pair-activity lookup).
Pairs
How many of the busiest pairs to scan (max 100). Only the top pairs by exchange count in the activity window are included.
Min Exchanges
Minimum trade count a pair must have in the ticker window to be considered active.
Min Profit BPS
Minimum estimated round-trip edge (basis points) between the attacker's front-run and back-run legs.
Rows
Page size for the results table after a scan completes.
Include AMM
When checked, AMM swaps are included. Uncheck to scan DEX offer trades only.
Advanced ledger override
Optional exact startLedger / endLedger bounds instead of date mapping.

How a scan works

  1. Resolve range — map dates (or ledger overrides) to ledger indexes.
  2. Find active pairs — GET /iou/ticker_data/all with an API-valid interval; sort by exchange volume; take the top Pairs.
  3. Fetch trades — for each pair, GET /iou/exchanges/{base}/{counter} with your From/To timestamps (up to 8,000 trades per pair).
  4. Detect patterns — look for same-taker opposite-side sequences with a victim trade between attacker legs (same or adjacent ledger).
  5. Estimate impact — XRP profit/loss where the pair is XRP-quoted; otherwise n/a.

API calls run client-side so rate limits apply per browser session (~180 requests per minute). Progress and the rate-limit counter reflect that budget.

Reading results

Score
Confidence (0–100%) from pattern strength: profit edge, ledger proximity, victim size, and optional sequence signals.
Profit XRP / Loss XRP
Estimated attacker profit and victim loss for XRP pairs. Fees are subtracted from profit where available.
Signal
Same ledger = all three legs in one ledger (stronger). Near ledger = adjacent ledgers.
Summary metrics
Totals across all candidates: alert count, same-ledger count, XRP-pair alerts, and summed profit/loss estimates.

Limits to know

  • Scans the top Pairs only — not every market on the XRPL.
  • Up to 8,000 trades per pair (8 paginated API pages). Very active pairs may be truncated.
  • Results are heuristic candidates; verify on-chain before treating them as confirmed front-runs.

Data source & thanks

Trade and ledger data are provided by the XRPL Data API from InFTF (Inclusive Financial Technology Foundation). Thank you to InFTF for operating this free, public REST API and making XRPL DEX/AMM history accessible.

This dashboard is an independent analysis tool and is not affiliated with or endorsed by InFTF.