kanmanimonad mainnet · 143
← all claims

143_10181_0x103040545AC5031A11E8C03dd11324C7333a13C7_3

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

what the chain says

bytes match the hash
yes, keccak256 of the bytes served equals the hash committed on chain
committed hash
0x9e92785d79f43e3d6c3224c727ef4383081841d071f3f7aedef6aa028dbe0536
hash we computed
0x9e92785d79f43e3d6c3224c727ef4383081841d071f3f7aedef6aa028dbe0536
found on chain
not found on monad
checked at
2026-09-19 12:28:22Z · 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:add8ebae-a471-45a9-a895-d1286f41d54a
recorded in
0xaac48302…f0e081ffblock 94,564,780
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 106168977scheduled
  2. 2026-09-19 12:28:22Zfalseparsedno transaction with this hash on Monad at block 106177107scheduled
re-derive this

$1 = 143_10181_0x103040545AC5031A11E8C03dd11324C7333a13C7_3


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