Transaction found
A retained transaction or receipt matches the transaction ID.
HOW INTEGRITY WORKS
What has been checked?
Integrity shows whether records match and how many checks passed.
Two checks today
Records match
Stored transaction and receipt records pass consistency checks.
Each passed check adds one to the count. Failed checks stay visible. Conditions without evidence are omitted.
What this tells you
Matching records can describe a failed transaction. Integrity checks the records; execution status shows whether the transaction ran successfully.
These checks do not establish buyer identity, service delivery or result quality. We will add conditions as reliable evidence becomes available.
Validation details
The first check matches a retained transaction or receipt to its hash. The second checks the stored receipt checksum, block identity and supported transaction/log links. The displayed count includes passed checks, with failures shown separately.
Evidence comes from one RPC source. Network consensus is not independently verified, and retaining a signature does not verify it. The API's legacy score field remains separate from this displayed check count.
Source coverage
x402scan provides a separate transaction sample; MPPscan provides service totals. Stripe account events and participant submissions stay private and do not change these public checks.
Amounts and dates
Selected stablecoins use a nominal $1 value. Unknown amounts remain unknown, and fees stay separate. Metrics cover up to 50,000 latest matches; exports include up to 10,000. Check source coverage when comparing dates.