Solana Explorer

Ordinary explorer search starts with an account, transaction signature or block. Inspector serves a different task: examining the transaction message a developer is preparing, including one that has not been submitted. Its input accepts a message encoded as base58 or base64, and provides examples for command-line, Rust and TypeScript workflows. A supported Squads transaction account can also be inspected.

Paste the message into Inspector Input. Invalid encodings or messages produce an error, while Clear removes the current input and its corresponding URL parameters. This helps keep separate investigations from accidentally sharing the previous transaction data.

Choose Simulate to evaluate the message against the latest confirmed state of the selected network. The output includes balance changes, detailed Logs and compute-unit profiling, which shows the execution resources consumed. Where an instruction contains an account the explorer cannot resolve, that profiling may be unavailable.

The simulation has two important boundaries: it persists no changes and disables signature checks. A successful result therefore does not prove that a real signed submission will be accepted, nor does it guarantee the same result after the network state changes. It is a debugging result, not a completed payment.

The Inspector’s simulation is free and its input workflow does not ask for an account. The explorer project uses the MIT license, allowing developers to inspect or adapt the code. Its account, transaction and block views remain useful when checking the actual on-chain result after a separate application submits a transaction.