A Solana transaction signature tells you which transaction to inspect, but it does not explain the steps that happened inside it. Transaction logs provide a readable trail of program messages and errors. They are useful when a swap fails, a token transfer behaves unexpectedly, or you simply want to understand an on-chain action.

What are transaction logs?

Solana programs can write messages while processing an instruction. A transaction may invoke several programs, and each can add log lines. An explorer or RPC response can display these lines alongside the transaction’s status. Logs are diagnostic output, not a separate transaction and not a guarantee that an action succeeded.

Think of a transaction as a small workflow. The signature identifies the workflow, the instructions describe requested actions, and logs show messages emitted as programs run. A log might show a program invocation, a custom message, a nested call, or a failure. The exact wording depends on the program; not every program writes detailed explanations.

How to find the logs

Copy the transaction signature from your wallet’s activity view, then search it in a reputable Solana explorer. Confirm that the page is on the correct cluster, usually mainnet for real assets. Open the transaction details and look for a logs or program activity section. Developers can also retrieve transaction metadata through an RPC method such as getTransaction, when the provider has retained the relevant data.

Never paste a seed phrase or private key into an explorer to inspect logs. A transaction signature is public data; signing credentials are not required. If a site asks for wallet access merely to display transaction history, stop and use another source.

Reading a basic execution trace

Invocation lines identify which program is executing. Indentation or invocation depth may show that one program called another through a cross-program invocation. A later success line means that particular invocation returned successfully; it does not necessarily mean every user-facing expectation was met. Read the overall transaction result as well as individual messages.

  • Program invoked: indicates execution began for a program.
  • Instruction data or message: may describe what the program attempted, but can be abbreviated or encoded.
  • Program success: confirms that invocation completed without returning an error.
  • Error: points to a failed instruction or nested call; the transaction’s final status is essential.

Logs may be terse; use decoded instructions and balance changes as context, then confirm the final result.

Understanding failures

Solana transactions are atomic: if an instruction fails, its state changes are rolled back, though the fee may still be charged. Errors may point to low funds, slippage, or program rules.

Use logs to form a hypothesis, then verify it against the transaction status, instruction details, and account changes. Do not infer success from one reassuring line.

For example, a swap can fail because its minimum-output condition was not met. The log may expose a custom program error, while the transaction summary shows failure and the token balances remain unchanged apart from any fee. This is a clue to review price movement and slippage settings, not a reason to retry blindly.

A safe troubleshooting checklist

  1. Verify the signature and cluster before interpreting details.
  2. Check the transaction’s final success or failure status.
  3. Identify the instruction and program nearest the error, including nested calls.
  4. Compare expected and actual balance changes; remember that failed transactions can still cost a fee.
  5. Use official program documentation for custom error meanings, and avoid sharing secrets with support accounts.

Logs are clues, not promises. For important transactions, compare a second trusted explorer or provider.