Transaction inspector
Inspect a synthetic transfer, its graph neighborhood and score.
Shared synthetic graph · CPU model
01
Compose a payment
About this scenario
Synthetic accounts from the seeded transaction graph.
Loading graph snapshot…
Synthetic data only. Scoring changes shared server state. Other visitors and repeat requests can change later scores. Reset affects fields only.
02
Inspect the scoring
Waiting for a payment.
No transaction scored
The network appears from a real server snapshot after you score a synthetic payment.
Up to six completed runs, kept in memory. Reloading or leaving clears the history. Nothing is saved to browser storage.