🔍 Fraud Monitor Results on the MultiversX Blockchain
Key stats from continuous on-chain surveillance, refreshed every minute. The same numbers are available via the public API.
What am I looking at?
This page summarises everything Fraudalysis has flagged since monitoring began. The numbers are deliberately split into alerts and scan cycles — a successful sweep is not a finding, so mixing the two would inflate the headline figure roughly twentyfold.
- Fraud Alerts Raised
- Findings where a detection rule actually fired. This is the number to watch.
- Scans Completed
- Full sweeps of the devnet. Routine housekeeping — shown for context, never counted as alerts.
- Rapid Senders
- Accounts pushing an unusual number of transactions in a short window.
- Peak Activity Hour
- The busiest hour of the last 24h, and how many findings landed in it.
Why does one alert count many times? On devnet, accounts are re-registered every scan, so the same pattern legitimately trips the same rule over and over. Repeated entries are expected and are not separate incidents. These are automated signals, not confirmed fraud — always verify on-chain before drawing conclusions.
📈 Activity Over Last 24 Hours
🎯 Alert Breakdown
📋 Most Recent Alerts — newest first
| Time | Severity | What happened | Account |
|---|---|---|---|
| Loading… | |||
How to read the table
- Time
- When the alert was raised, in your local timezone. Newest first.
- Severity
- How strongly the pattern matched, not proof of wrongdoing.
- What happened
- The specific pattern that triggered the rule, in plain language.
- Account
- The MultiversX address responsible. An address repeats when one account trips a rule repeatedly.
Only the most recent alerts appear here. For the complete record with full filtering and paging, see the Live Monitor.