kanmanimonad mainnet · 143
← all claims

143_10182_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
0x6004e1bd68109bd03e36d7e58a491f0e37ff3a936347f20674562a53ad3c1cc7

what the chain says

bytes match the hash
yes, keccak256 of the bytes served equals the hash committed on chain
committed hash
0x2d5b0277656022832dce1e08a7e35404ead4955f843eef40780425c4d8685979
hash we computed
0x2d5b0277656022832dce1e08a7e35404ead4955f843eef40780425c4d8685979
found on chain
not found on monad
checked at
2026-09-19 12:28:23Z · 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
#10182
left by
0x1030…13C7
score
95
revoked
no
tags
agent_rating:research · task:5644b36f
endpoint
task:5644b36f-17d4-4725-a52e-cfd8c8e1bde2
recorded in
0x1423a6a6…adb3ca4dblock 94,567,525
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:23Zfalseparsedno transaction with this hash on Monad at block 106177107scheduled
re-derive this

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