kanmanimonad mainnet · 143
← all claims

143_10181_0x103040545AC5031A11E8C03dd11324C7333a13C7_2

false

No transaction with this hash on Monad at block 106177093.

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

what the document says

declared network
monad
cited transaction
0x24041ea63efda31829cde548a502d2018c80f85cc59f18c6c79fc33a36ea8c95

what the chain says

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

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
88
revoked
no
tags
worker_rating:research · 0xaf95b213
endpoint
task:0304d832-996e-4ba8-97b8-c016508ffb71
recorded in
0xb9a60d58…f99797dfblock 94,562,709
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:27Zfalseparsedno transaction with this hash on Monad at block 106168964scheduled
  2. 2026-09-19 12:28:21Zfalseparsedno transaction with this hash on Monad at block 106177093scheduled
re-derive this

$1 = 143_10181_0x103040545AC5031A11E8C03dd11324C7333a13C7_2


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