kanmanimonad mainnet · 143
← all claims

143_10168_0x103040545AC5031A11E8C03dd11324C7333a13C7_1

false

No transaction with this hash on Monad at block 106177093.

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

what the document says

declared network
monad
cited transaction
0xbb9f9d42710b3ef0e4124c8e21b8ba36f16036c20ec24f2e24569a287e5dcf5c

what the chain says

bytes match the hash
yes, keccak256 of the bytes served equals the hash committed on chain
committed hash
0xb357198d7fb50e38df823387c593a0f8aafdc0da2a57e7ee9c7af5539508ab6c
hash we computed
0xb357198d7fb50e38df823387c593a0f8aafdc0da2a57e7ee9c7af5539508ab6c
found on chain
not found on monad
checked at
2026-09-19 12:28:21Z · block 106,177,093

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
#10168
left by
0x1030…13C7
score
95
revoked
no
tags
agent_rating:research · task:b9cb127d
endpoint
task:b9cb127d-9f94-4be4-b15c-c061e51e472b
recorded in
0x39ac62a6…96612c00block 94,562,553
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:27Zfalseparsedno transaction with this hash on Monad at block 106168964scheduled
  2. 2026-09-19 12:28:21Zfalseparsedno transaction with this hash on Monad at block 106177093scheduled
re-derive this

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