kanmanimonad mainnet · 143

Verify

Paste an evidence document or a claim id from this site. The check that runs here is the same code the sweep and the command line run, so this page and the tool cannot give different answers. The result gets its own URL, so it can be sent to whoever disagrees.

try one that resolvestry one that does not

checking claim 143_10182_0x103040545AC5031A11E8C03dd11324C7333a13C7_2 with its on-chain commitment

unknownparsed

No RPC configured for Monad.

We could not look or could not read. This is never an accusation.

what was read

bytes
792 bytes
media type
not stated
resolved via
http
mapping
execution-market.v1
hash check
the bytes served match the hash committed on chain
computed
0xbe5d8f316855def0c12cfa77648fe12f2ec99d49c214b25ce2149dd2d9f13688

what it claimed and what the chain said

declared network
monad
cited transaction
0xd0df29941ce99c861c32d021a3363053e1525a4bf4e1c2e886d5cc823fcf1847
found
not looked for
checked at
2026-09-22 12:26:00Z

run the same check yourself

node --experimental-strip-types verifier/src/cli/locate.ts monad 0xd0df29941ce99c861c32d021a3363053e1525a4bf4e1c2e886d5cc823fcf1847

what a negative was tested against

A transaction that is not found means nothing without the list of chains it was looked for on. Publishing the coverage is what makes a false falsifiable.

Monad · 143Ethereum · 1OP Mainnet · 10Base · 8453Arbitrum One · 42161Polygon · 137BNB Smart Chain · 56
re-derive this

The verdict object exactly as the API returns it. Same shape, same fields, same code path.

{
  "checkedAt": "2026-09-22T12:26:00.604Z",
  "declaredNetwork": "monad",
  "declaredTx": "0xd0df29941ce99c861c32d021a3363053e1525a4bf4e1c2e886d5cc823fcf1847",
  "mapping": "execution-market.v1",
  "hashMatches": true,
  "computedHash": "0xbe5d8f316855def0c12cfa77648fe12f2ec99d49c214b25ce2149dd2d9f13688",
  "rung": "parsed",
  "outcome": "unknown",
  "reason": "no RPC configured for Monad"
}