Free tool
This Solana transaction inspector takes a mainnet signature and shows what the transaction cost and did: the fee split, compute units, any Jito tip, each instruction with its program named, balance changes, and the logs.
No sign-up. Runs in your browser. Last reviewed by the Builderz team.
The tool asks a Solana mainnet RPC node for the transaction with the getTransaction method, using jsonParsed encoding and confirmed commitment. Our server makes the call and returns a summary, not the raw response. Nodes only keep recent history, so old signatures can come back not found.
The base fee is 5,000 lamports per signature. The priority fee is the compute unit limit times the unit price in micro-lamports, divided by 1,000,000. The tool reads the limit and price from the compute budget instructions, subtracts the base fee from the total fee, and checks that the two agree.
A Jito tip is a plain System Program transfer to one of eight published tip accounts. The tool adds up every transfer to those accounts, in lamports. The tip is paid on top of the network fee, so it is shown separately and added to the one-line total.
The RPC node decodes the System, Token, Token-2022, Associated Token, and Memo programs. It does not decode the compute budget program, so this tool reads those bytes itself. Programs the node does not know, including most Anchor programs, show as raw instructions with the program id only.
The signature goes to our server and from there to the RPC node. Nothing is stored by this tool. A signature is public on chain, but the lookup still tells those two parties that you asked about it.
The signature may be mistyped, from another cluster such as devnet, not yet confirmed, or older than the RPC node keeps. Public nodes keep limited history. An archive provider can still have it.
The transaction set no compute unit price, or the price was zero. Then the fee is only the 5,000 lamports per signature. Wallets and apps often skip a priority fee when the network is quiet.
The name comes from a short list of well-known programs. A program outside that list shows its id only. The id links to the address checker, and an explorer can usually tell you more.
Not yet. Anchor instruction data needs the program IDL. The IDL inspector reads the layouts of a published IDL, which is the first step toward decoding.
Beyond the tool
$5K-$15K. Book an intro call, or send a brief with what the tool showed you. We reply within one business day.
Acceptance in writing
Criteria agreed before build starts
Proposal in 48h
After a qualified scoping call
Change control
Scope, exclusions, and owners named