Sigread

Gallery 07 · Transactions, explained

Paste a Solana transaction. Read what it did, in plain words.

For anyone holding a transaction link who wants to know who paid, what moved and what it cost. Nothing to install and nothing to sign.

Reads Solana mainnet directly, names each program it finds, and lists every balance change and fee.

Explain a transaction
Acc. no. 0000 Fetching a live transaction…
translated

A wallet swapped one token for another through a trading app and paid a small network fee.

Each card is a real recent transaction read from Solana mainnet.

How it works in 3 steps

  1. I

    Paste a transaction ID

    The long code from a wallet, explorer or chat message.

  2. II

    We read it from Solana

    Every program, account and balance change gets named.

  3. III

    You get a plain sentence

    Plus who paid, what moved and the exact fee.

Nothing is moved or charged. This site only reads public data and never asks you to sign.

How it works

From a string of letters to a sentence you can repeat.

  1. 1 · The raw record. A transaction is stored as compact bytes. Its ID, the signature, is how you find it.
  2. 2 · The cast list. We list every account it touched and mark who paid and who signed.
  3. 3 · The programs. Each instruction calls a program. We match its ID to a known name.
  4. 4 · The money. Balances before and after are compared, so every SOL and token change shows up.
  5. 5 · The label. All of that is summed into one plain sentence, with the fee split out.

Cat. 01 · The reader

Explain a transaction

What this does: you paste a transaction ID and it tells you, in words, what happened and what it cost.

Try an example:

Examples are picked live: the newest successful transaction for that kind of program, seconds old.

Your explanation appears here as a labelled card.

Cat. 02 · Wallet history

Explain my last transaction

What this does: shows the latest transactions of any wallet and explains the one you pick. Connect your wallet to fill it in.

The ten newest transactions will be listed here, newest first.

Cat. 03 · Identification desk

What is this string?

What this does: tells you whether a code someone sent you is a transaction, a wallet, a coin or a program, and catches typos.

Try an example:

The result names what it is and what to do next.

Anatomy of a Solana code

Solana writes binary data in base58. Decoding it gives a fixed number of bytes, and the count tells you what the code is.

32 bytes · an address (wallet, coin, program)
64 bytes · a transaction ID

The check runs in your browser. Only addresses are looked up on chain, to see what kind of account they are.

Cat. 04 · The register

Who is this program?

What this does: looks up the programs that transactions call, says what each one is for, and checks any program ID live on chain.

Try an example:

Flowcharts

Two diagrams, drawn plainly.

A. How a reading happens
B. Where the data goes, and where money never goes

Glossary

The words on the labels

Signature
The ID of a transaction. It is also the proof that the payer approved it.
Fee payer
The first signer. They pay the network fee, even if the transaction fails.
Slot
A short time window (well under a second) in which one validator adds a block.
Program
Code on Solana. Swaps, coins and transfers are all programs being called.
Priority fee
An optional tip on top of the base fee to get processed sooner.
Compute units
How much work the transaction asked for. Priority fees are priced per unit.
Mint
The address of a coin. All copies of that coin point back to it.
Token account
A small box that holds one coin for one wallet. Opening one costs a refundable deposit (rent).
Lamport
The smallest unit of SOL: one billionth of a SOL.
Inner instruction
A step that one program called inside another, like a router calling a pool.

Roadmap

What is on the wall, and what is still in the workshop

  1. On display

    Phase I · The reader

    • Plain sentence for any transaction
    • SOL and token changes per account
    • Fee and priority fee split
  2. On display

    Phase II · Context

    • Wallet history with one-click explain
    • String identification desk
    • Program register with live check
  3. In the workshop

    Phase III · Deeper labels

    • Named steps for more trading programs
    • Clearer wording for failed transactions
  4. Planned

    Phase IV · Sharing

    • Printable label card image
    • Side-by-side reading of two transactions
  5. Planned

    Phase V · Languages

    • Sentences in more languages
    • A short glossary in each

Tokenomics

The coin, catalogued

Planned structure. No coin address has been published yet, so nothing below is live.

0fixed supply
Sold on the public curve
About 0% of supply, to anyone, at the same rules; no presale
Added as liquidity
About 0% paired into a trading pool when the curve completes
Team allocation
0% set aside; the team only holds what it buys on the curve like anyone else
Mint and freeze rights
Switched off, so no one can print more or lock your coins
Liquidity at graduation
Locked or burned when the curve completes

A coin is not an investment product. Nothing here promises any return.

FAQ

Questions visitors ask at the desk

What is this, in one sentence?

A free reader that turns a Solana transaction ID into a plain sentence about who paid, what moved and what it cost.

Is it safe? Does it touch my money?

It only reads public records. Connecting a wallet shares your public address so the history tool can fill itself in; the site never requests a signature or a transaction, and it cannot move anything.

Where does the information come from?

Straight from Solana mainnet, through a read-only relay on this site. Coin names come from a public token list and are matched by address, not by name.

Why does it say "about" next to some amounts?

When a transaction also opens or closes token accounts, a small refundable deposit moves with it. We separate the fee exactly, but deposits can blur the swap amount slightly.

A program shows as "unknown". Is that bad?

Not by itself. It only means the program is not in our register yet. The register desk can still confirm on chain that it is real code.

Can it read very old transactions?

Usually yes. Very old records may not be served by every node, and the reader will say so if the lookup comes back empty.