Identity & evidence3 min read

MEV and Transaction Ordering: What Data Can Show

Analyse transaction ordering and execution patterns without assuming that adjacency alone proves strategy, common ownership or harmful intent.

Editorial illustration accompanying mev and transaction ordering: what data can show.

Overview

When translating these concepts into an integration, keep the scope described by the wallet history api with the result. The examples in wallet transaction history and smart contract event logs show how the same distinction affects neighbouring data questions.

Transaction order can affect execution outcomes. Data can reveal order, asset movements and repeated patterns, but attributing strategy or intent requires more than two transactions appearing next to each other.

Separate observable and inferred facts

Accepted block order, calls and transfers are observations. A sandwich or arbitrage label is an interpretation requiring a defined rule and sufficient execution context. Preserve the evidence behind any classification. A pending-pool observation can add context, but it is not a universal view of every transaction before inclusion.

Worked example: adjacent trades

Two trades surround another swap in a block. That ordering is a candidate pattern, not alone a complete proof of a particular strategy or actor relationship. A review checks assets, routes, quantities and resulting effects before assigning a documented analytical label.

Make analysis reproducible

Record block identity, ordering fields, traces where used and classifier version. Test unrelated adjacent trades and composed routes. Keep confidence or unresolved status explicit. Do not turn a heuristic label into a definitive accusation about an identified person. Reports should allow inspection of contributing evidence and distinguish measured execution effects from inferred motivation.

A practical acceptance test

Create one candidate surrounding-trade pattern and one unrelated adjacent sequence. The classifier should expose its rule, evidence and uncertainty rather than assert actor identity. Change its threshold in a new version and compare results without changing raw order. Pending observations from one node must not be described as a complete pre-inclusion market view.

Questions about the topic

Frequently asked questions

Does adjacency prove a strategy?

No. It is one possible signal requiring context.

Can all pre-inclusion activity be observed from one node?

No. Pending views are incomplete and node-specific.

Standards & technical documentation

Further reading

{{TODO: author name}}

Practical explanations of blockchain data, software integration and the context behind a record.

About Indexbase
← Back to all articles

Build with better context.

Get an update when private beta opens.

Form setup in progress. Nothing entered here is sent or saved. {{TODO: endpoint}} See the full form and email alternative.