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.
These Tempo checks use retained evidence 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
The transaction API combines retained Tempo RPC records with source-reported external transactions. Their evidence strength and coverage differ. MPPscan service totals remain a separate measure. 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 include all matching retained observations. Paid report limits and formats are stated in the live catalog and quote. Check source coverage when comparing dates.
Analytics and time windows
Today begins at 00:00 UTC. Seven-day and thirty-day totals roll back from the update time, without a daily reset. They sum all retained matching records with exact decimal arithmetic; no 50,000-row cap applies.
Partial history means the requested window extends before collection or crosses a gap. Missing time is never estimated as zero. Average transaction rate divides eligible Tempo observations by minutes of contiguous retained Tempo block time, excluding the opening timestamp and gaps. At least one covered minute is required. This continuous-coverage measure does not establish complete external-network coverage; external backfill can add records to earlier windows.
Average size divides the nominal total by transactions with known values, including known zero amounts. The median uses that same known-value set; unknowns enter neither statistic. Transaction identities are keyed by network and hash, which does not deduplicate separate attempts into economic purchases. Active wallets counts distinct initiating addresses, not people or verified agents. Stablecoins use nominal $1 values; fees stay separate. Histogram intervals adapt to the selected period. Analytics snapshots refresh every ten seconds.