kanmanimonad mainnet · 143
← all claims

143_10183_0x103040545AC5031A11E8C03dd11324C7333a13C7_1

false

No transaction with this hash on Monad at block 106177163.

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

what the document says

declared network
monad
cited transaction
0xeb075ccba412c75300603c2f99ad72d810d27847f82a6917b1a8958b6b8a72e4
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
0x77ea587cd4d27c6455196d9942a3439dd91e4764d98f868a47b252d519987a26
hash we computed
0x77ea587cd4d27c6455196d9942a3439dd91e4764d98f868a47b252d519987a26
found on chain
not found on monad
checked at
2026-09-19 12:28:40Z · block 106,177,163

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
#10183
left by
0x1030…13C7
score
70
revoked
no
tags
worker_rating:research · 0xfa1c6ff4
endpoint
task:76743d5b-61c8-46f2-ae85-9b65e31d6147
recorded in
0xf25505ed…1608b2d9block 101,728,656
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:46Zfalseparsedno transaction with this hash on Monad at block 106169033scheduled
  2. 2026-09-19 12:28:40Zfalseparsedno transaction with this hash on Monad at block 106177163scheduled
re-derive this

$1 = 143_10183_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