kanmanimonad mainnet · 143
← all claims

143_10181_0x103040545AC5031A11E8C03dd11324C7333a13C7_9

false

No transaction with this hash on Monad at block 106177107.

We read that chain successfully and the cited transaction is not there.

what the document says

declared network
monad
cited transaction
0x6f9535b8ba6fb15d0a29a1d338b20fd92b08050b70f3c814f41f133c1e95c103

what the chain says

bytes match the hash
yes, keccak256 of the bytes served equals the hash committed on chain
committed hash
0x471c0c0c29f6ee8fb7aab39680cc8d90efa56c9a0e4c6969173f21e6527b0c11
hash we computed
0x471c0c0c29f6ee8fb7aab39680cc8d90efa56c9a0e4c6969173f21e6527b0c11
found on chain
not found on monad
checked at
2026-09-19 12:28:24Z · block 106,177,107

A verdict is a measurement at a time, so both the wall clock and the block are recorded. Without the block, "not found" is unfalsifiable: a reader cannot tell whether we looked before the transaction existed.

the feedback itself

As the Reputation Registry recorded it.

about agent
#10181
left by
0x1030…13C7
score
89
revoked
no
tags
worker_rating:research · 0xaf95b213
endpoint
task:de18cded-ddcc-4a1c-83e5-9b2879da179d
recorded in
0x3d94ab91…3a35c1ccblock 94,829,083
operator reply
none. The registry gives the agent an on-chain right of reply and it is rendered here when used.

verification history · 2 checks

Append only. A re-check writes a new row and never edits an old one, so a document somebody repairs reads as a change with both timestamps rather than as a number quietly improving.

  1. 2026-09-19 11:47:29Zfalseparsedno transaction with this hash on Monad at block 106168977scheduled
  2. 2026-09-19 12:28:24Zfalseparsedno transaction with this hash on Monad at block 106177107scheduled
re-derive this

$1 = 143_10181_0x103040545AC5031A11E8C03dd11324C7333a13C7_9


SELECT id, rung, outcome, reason, checked_at, checked_at_block, automatic,
       mapping, found_chain, found_block
FROM fovea.verdict
WHERE feedback_id = $1
ORDER BY checked_at ASC, id ASC