SOLANA / EXECUTION RECEIPTSONE SIGNATURE. EVERY REPORTED CHANGE.
A Solana transaction can touch multiple accounts and programs. PLIX turns its execution data into a receipt you can read.
Read the chain.Paste a transaction signature from your wallet or explorer.
Ready. No wallet connection or signature request.
Real RPC data. Receipts are shown only at finalized commitment. No simulated activity.
YOUR EXECUTION RECEIPT
Net lamport changes include fees, account funding and rent returns. They are not a trading profit calculation.
Instructions are listed from the transaction message and recorded inner calls. On failure, the list may include instructions that were never executed. Unparsed instructions are left explicit.
Before and after, straight from execution metadata.
Surface the inner calls behind one signature.
Separate successful execution from finality.
BUILT AROUND SOLANA / EXPLAINED
A transaction is more than its headline. PLIX keeps the execution details attached to the result.
PLIX looks up a Solana transaction using its signature. The server checks the RPC network and requests a parsed transaction at finalized commitment, supporting legacy and version-0 transactions.
The receipt groups the network fee, account balance changes and instruction path. Every result includes an explorer link so you can inspect the source transaction.
For SOL, PLIX subtracts each account’s pre-transaction balance from its post-transaction balance. Lamports are displayed as SOL. The network fee is shown separately, but is already part of the fee payer’s net balance change.
SPL token changes are matched by account index and mint. Quantities are calculated from raw integer token amounts using the recorded decimals. Mint addresses identify tokens without relying on potentially misleading ticker names.
If one side of a token balance is absent, PLIX shows it as unreported and does not invent a zero. Account creation, closure, wrapping and rent can affect how you interpret the receipt. Net changes are not a complete transfer history or profit calculation.
The transaction message contains top-level instructions. Programs can also call other programs during execution; recorded inner instructions expose those calls.
PLIX places inner calls under their parent instruction and shows the program address and parsed instruction type when the RPC provides it. This helps you follow token transfers and account operations that sit behind a single application action.
Custom program instructions may remain unparsed. PLIX shows that limitation instead of assigning a guessed swap, purchase or burn label.
A finalized transaction can still have an execution error. PLIX displays the execution result separately and includes the reported error when present. Failed execution must not be read as a completed trade; network fees can still be charged.
If a finalized receipt is unavailable, the interface reports that state. The transaction may not yet be finalized, the network may be wrong, or the RPC may not retain the requested history.
Download a JSON receipt to retain the exact normalized result returned by PLIX. It records the network, signature, slot, queried time and reported changes. It is not a signed certificate; use the chain record as the reference.
No. PLIX describes transaction data. A successful transaction or a familiar program address does not establish that a token, app or investment is safe.
No. You supply a public transaction signature. The server sends that signature to the selected network’s RPC provider. No signing, transfers or token approvals are requested.
Check the network and signature. The public RPC may be rate-limited or lack historical data. A dedicated RPC with transaction history can be configured for production.
WHY PLIX EXISTS
A wallet says “confirmed.” You still want to know what moved, what cost SOL and which programs were involved.
PLIX is the receipt layer for that moment. Built around Solana’s accounts, token balances and instruction paths, it gives you a structured view of execution you can inspect and keep.
Read a transaction ↑