kanmanimonad mainnet · 143
← all claims

143_10181_0x103040545AC5031A11E8C03dd11324C7333a13C7_5

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

what the chain says

bytes match the hash
yes, keccak256 of the bytes served equals the hash committed on chain
committed hash
0xf3a4d4fe00d1586fe92310176dc33bf2af50b4fb8a7bfac902edf7bfc6a2fd85
hash we computed
0xf3a4d4fe00d1586fe92310176dc33bf2af50b4fb8a7bfac902edf7bfc6a2fd85
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
85
revoked
no
tags
worker_rating:data_collection · 0xaf95b213
endpoint
task:001c5b49-2c9d-487d-aa69-fbca52fc180e
recorded in
0xe0c20689…1d90ef01block 94,566,762
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:22Zfalseparsedno transaction with this hash on Monad at block 106177107scheduled
re-derive this

$1 = 143_10181_0x103040545AC5031A11E8C03dd11324C7333a13C7_5


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