kanmanimonad mainnet · 143
← all claims

143_10182_0x103040545AC5031A11E8C03dd11324C7333a13C7_40

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
0x3bb9dbf88d1d9dac63613676ebbf14661baf5765dda54f72928848a5b0cf6af2
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
0x1c5e80bd8fedf5d151ed9fe49bbb923d9fd60b746e6c06e6106f6c000141a3fc
hash we computed
0x1c5e80bd8fedf5d151ed9fe49bbb923d9fd60b746e6c06e6106f6c000141a3fc
found on chain
not found on monad
checked at
2026-09-19 12:28:42Z · 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
#10182
left by
0x1030…13C7
score
70
revoked
no
tags
worker_rating:research · 0x350ef06f
endpoint
task:46e72422-e5fc-48b1-bb64-ce1da177e6eb
recorded in
0x4a5b0112…b715246dblock 103,091,468
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:49Zfalseparsedno transaction with this hash on Monad at block 106169047scheduled
  2. 2026-09-19 12:28:42Zfalseparsedno transaction with this hash on Monad at block 106177163scheduled
re-derive this

$1 = 143_10182_0x103040545AC5031A11E8C03dd11324C7333a13C7_40


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