kanmanimonad mainnet · 143
← all claims

143_10180_0x103040545AC5031A11E8C03dd11324C7333a13C7_1

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
0x4481e2a016856984c535ce163cabd24502299399f0ad9133fb455870d92f0a0c
read by mapping
execution-market.v1

what the chain says

bytes match the hash
yes, keccak256 of the bytes served equals the hash committed on chain
committed hash
0x5ecd7ad3da68f1395d5eac859f2a431032cf37e1a55ee0840b522f912b19ab83
hash we computed
0x5ecd7ad3da68f1395d5eac859f2a431032cf37e1a55ee0840b522f912b19ab83
found on chain
not found on monad
checked at
2026-09-19 12:28:25Z · 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
#10180
left by
0x1030…13C7
score
90
revoked
no
tags
worker_rating:research · 0x76e9be89
endpoint
task:d6115078-d23e-4ef2-8634-245846269c18
recorded in
0x5c6e5f24…322134eeblock 97,684,424
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:31Zfalseparsedno transaction with this hash on Monad at block 106168977scheduled
  2. 2026-09-19 12:28:25Zfalseparsedno transaction with this hash on Monad at block 106177107scheduled
re-derive this

$1 = 143_10180_0x103040545AC5031A11E8C03dd11324C7333a13C7_1


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