hashlock.pronodealgo.xyz

Algorand

From vet402-algorand, a separate project; graded apart from Solana, Tempo and Base. Listed on the Algorand page.

vet402 paid this seller 4 times with its own money (Algorand 4), most recently on 2026-09-28 (UTC). 2 with a settlement receipt; 2 came back with an answer.

It costs the seller nothing, and there is nothing to sign up for.

… measuring · Measuring: a rank number needs 10 counted purchases on 2 different days; this seller has 2 on 1.

Came back, of counted, per chain: Algorand 2/2. Came back with an answer = vet402's payment settled, then the seller answered 2xx with a non-empty body. vet402 did not check that the answer is what the listing promised; whether its keys matched what the seller declared is a separate column.

Separate column, not in the grade. Answer matched what the seller declared: not checked.

Not counted

Counted against this seller

None.

How each failure is assigned

Recent purchases

Each tx links to a public explorer.

1. 2026-09-28 01:29 UTC · Algorand · came back with an answer S32NIXXZ…7GC63Q
   https://hashlock.pronodealgo.xyz/hashlock-algo-mainnet/api/timestamp-batch
2. 2026-09-28 01:26 UTC · Algorand · came back with an answer 3IM7PLWJ…5MBMLA
   https://hashlock.pronodealgo.xyz/hashlock-algo-mainnet/api/timestamp
3. 2026-09-27 05:00 UTC · Algorand · can't tell: request rejected 4xx
   https://hashlock.pronodealgo.xyz/hashlock-algo-mainnet/api/timestamp-batch
4. 2026-09-27 04:40 UTC · Algorand · can't tell: request rejected 4xx
   https://hashlock.pronodealgo.xyz/hashlock-algo-mainnet/api/timestamp

Are you the seller?

Is a row wrong? A seller who thinks a row is wrong opens a GitHub issue with the URL or tx. vet402 checks it against the chain and the raw result; a wrong row is fixed and the fix is noted in the change log.

Tell vet402 a row is wrong (GitHub issue, prefilled)

Signed records of failed purchases are published only after the seller is told. More for sellers