Inspect a Solana transaction.
Start with a signature. Verify against the event you expect.
Transaction request
A signature and its network are enough to begin.
Try a devnet example
What can this inspector find?
It reports transaction finality, execution status, programs observed in complete logs, and possible Anchor log-event bytes. Candidate bytes are discovery only—not proof of event identity.
Native transfers, protocol-specific formats, and Anchor CPI events may have no supported candidate. You can still inspect the transaction without reaching a compulsory event field.
Read Anchor’s event documentation ↗Inspection evidence
Transaction facts first. No assumed event.
Your evidence starts here.
We’ll show its finalized status, execution outcome, observed programs, and any unverified event candidates.
Inspection is useful even when no supported event exists.
Know when
to act.
Verification checks evidence. Your application owns the decision.
Read the integration guideThe expected event passed its checks. Apply your own authorization and replay policy before acting.
Available evidence disproved the requested event. Stop the protected action and use the reason code to investigate.
The evidence was not strong enough to decide. Do not act. Retry or escalate according to the reason code.
Verified: The expected event passed its checks. Apply your own authorization and replay policy before acting.