x402receiptsReceipt verification

Receipt 62da0d5e…b99b04

Checking in your browser…
The receipt
When24/09/2026, 09:14:13 UTC
Whatscrape.actor.run/v2/run
Amount0.006 USDC
Paid by0x0d3m0a…a9b1d3
Paid to0x4d5e00…0ee4d4
Deliveredyes (HTTP 200)
Fingerprintefbc3f8520…b9735594
Receipt id 62da0d5e-74aa-4434-8d43-f1a107b99b04
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  efbc3f8520618b3f8fd38a105d95c991d74e2337e10ab57acdfccbe8b9735594
  2. right a8e741c12d56f1e6179e32fd30a40e8a432d09b44d5f8dd107c72e0eaf8af61a
  3. left  5d5781b07eb2f74b6b6c8a39f21eb17c268c0b02a96ed4e9b895439a717c6db7
  4. right 3a0db43292237b5300edd0cf5d4101202e48665eceb8f62f968695747c5914d8
  5. right 9ba1cc4ffa5abbb31c9fb72b07ea8e92d69ab2436cf44f2655f08d9de515f1b9
  6. right 2e94dfc63666c1600f61e9ff5e363f193a3473279c23689c66ca58c3bfd805ce
  7. right bea8c40cd66088a79e7c0a7f2f7813d73a5289c6c2d3373c4c8e7d5e268588b7
  8. root  f2af185d28bed14f77ef6ee7901f82fec9fc88a1a6ae4ceb1904e74fc6124d46