kanmanimonad mainnet · 143
← all claims

143_10181_0x103040545AC5031A11E8C03dd11324C7333a13C7_6

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
0x0b5ce3611c0b79637f3a43dfdd9a396a8b831d0e3d924426910dc1317dfce09f

what the chain says

bytes match the hash
yes, keccak256 of the bytes served equals the hash committed on chain
committed hash
0xcfc64c2caee540c38759b35b7e1d83ef04fdd63c3ff497aa79ee5843741ff277
hash we computed
0xcfc64c2caee540c38759b35b7e1d83ef04fdd63c3ff497aa79ee5843741ff277
found on chain
not found on monad
checked at
2026-09-19 12:28:23Z · 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:d1de3cde-200b-4f05-9478-523536c673f1
recorded in
0x195dbf56…b94c0baablock 94,568,542
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:28Zfalseparsedno transaction with this hash on Monad at block 106168977scheduled
  2. 2026-09-19 12:28:23Zfalseparsedno transaction with this hash on Monad at block 106177107scheduled
re-derive this

$1 = 143_10181_0x103040545AC5031A11E8C03dd11324C7333a13C7_6


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