x402receiptsReceipt verification

Receipt a3f8709f…4eb3c7

Checking in your browser…
The receipt
When24/09/2026, 09:24:36 UTC
Whatapi.exa.ai/search
Amount0.004 USDC
Paid by0x0d3m0a…a9b1d3
Paid to0x1a2b00…0ee1a1
Deliveredyes (HTTP 200)
Fingerprint85ff7ad5d9…6cbe86b5
Receipt id a3f8709f-ea18-4f9f-8786-2ee6704eb3c7
On the ledgerHedera testnet
Batchbd9d9f01…fa5c · 59 receipts
Rootf2af185d28…c6124d46
Topic0.0.10714216 · message #4
Consensus time25/09/2026, 19:10:13 UTC
Open the transaction on HashScan ↗Open the group (59 receipts)All messages on this topic ↗
The ledger holds only the root — a fingerprint of the whole batch. What was bought stays private; that it existed, unchanged, at this time is public.
For auditors: the path from this receipt to the ledger root
Path from this receipt to the root

sha256 of the receipt's canonical JSON gives its fingerprint. Each step pairs it with a sibling (left or right) and hashes again; an odd node pairs with itself. The last result must equal the root above. This group was anchored before the log moved to RFC 9162, so it keeps the earlier rule.

  1. leaf  85ff7ad5d9c4bbb91c006b37b105bb4458fbe3550146f9a852af13686cbe86b5
  2. right 7dc84a4891120798dce58abece5ac8879dcf575455bac8240be7ca8cecb31f3a
  3. left  411debf72c7a0cc5e3128a7b6f1db2bd8a0e1c2aa0adf4bd807e3a4407e5df6b
  4. left  d39d0f6594d187cc329bda0c03ad12e6055f1ae165e5d3d6e51f01ace87c96c1
  5. left  1d5c568c417ac751cb7e63fdae33ee9bca1b354bf7f8e9d0e971986a7a6f51c2
  6. right 2e94dfc63666c1600f61e9ff5e363f193a3473279c23689c66ca58c3bfd805ce
  7. right bea8c40cd66088a79e7c0a7f2f7813d73a5289c6c2d3373c4c8e7d5e268588b7
  8. root  f2af185d28bed14f77ef6ee7901f82fec9fc88a1a6ae4ceb1904e74fc6124d46