x402receiptsReceipt verification

Receipt a102dd17…0ab9e2

Checking in your browser…
The receipt
When24/09/2026, 09:27:28 UTC
Whatapi.exa.ai/search
Amount0.004 USDC
Paid by0x0d3m0a…a9b1d3
Paid to0x1a2b00…0ee1a1
Deliveredyes (HTTP 200)
Fingerprint1d8d01559e…4a5f651d
Receipt id a102dd17-726c-4db0-9875-3b7fe90ab9e2
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  1d8d01559ef6f1d433063d90e8877eeee43014823debbae575c11eab4a5f651d
  2. left  08e5aa87d7af523f9437e396bb84c6adfbdcdeb1b47d6c81d5bc74df6e85be97
  3. right 96ae2932608a9ddacb99edf0ff4057e0e8471baf9282cc5b0f560046be0d7db1
  4. right 0474ace816b15c1a31f29edf86c9fd918ce6a4ee1eedeec96b2ce56c90867bb1
  5. right a88417e40b80fcc343ec042fbb60422290bb5794b2a3a80066fffdde40d8deb2
  6. left  09455c3fa7e9477fadac48ef4ede76dd8069e2e96a922e3fea7837884c926fdb
  7. right bea8c40cd66088a79e7c0a7f2f7813d73a5289c6c2d3373c4c8e7d5e268588b7
  8. root  f2af185d28bed14f77ef6ee7901f82fec9fc88a1a6ae4ceb1904e74fc6124d46