Transaction verification

How to verify a finalized Kashnio transaction

A transaction should be treated as final only when its explorer record is bound to a certified finalized checkpoint—not merely because an RPC endpoint accepted it.

Published August 25, 2026 · Kashnio technical review

Start with the transaction ID

Obtain the transaction ID from the wallet or service that submitted the transfer. Never use a seed phrase, private key, password or recovery code to verify a public transaction. Public verification requires only public identifiers.

Open the official explorer

Use the official Kashnio transaction explorer and search for the exact identifier. Check every character rather than relying on a shortened display.

Separate admission from finality

An admitted or pending transaction is not yet final. The record should explicitly show finalized inclusion and identify the checkpoint that contains the executed state transition.

Check the checkpoint

Open the associated checkpoint and verify its height, checkpoint identity and state root. The explorer obtains validator participation from finalized chain state; it must not count a candidate or configuration file as a validator.

Confirm the result

Safety boundaryThe explorer is a public inspection tool. It will never need a private key or recovery phrase. For allocation questions, use the official Kashnio support page.