Solana transaction receipt

What the receipt shows

• A signature here is base58 and about eighty-eight characters long — it looks nothing like a hexadecimal hash, which is why the field recognises it on sight and does not have to ask.
• One transaction can carry many instructions and touch many accounts. The receipt keeps them in order, because the order is what makes the sequence readable at all.
• Fees are small and fixed enough that they are rarely the story. What the paper is for here is the account list and the amounts, and those are what it leads with.

Address format

base58 (32–44)

Native unit

SOL

How to issue one

1. 1Paste the transaction hash or the wallet address into the field. Which of the two it is is recognised from its shape — there is nothing to choose.
2. 2Press issue. We read the chain once and assemble everything the page needs in a single request.
3. 3The PDF downloads. Every party is named where we hold a name for it, and every figure carries the price at the time of the transaction, not today's.

Questions

Do I need an account?

No. The field works for anyone, signed in or not, and the receipt downloads straight to the device.

Is what I paste stored?

The hash reaches our server because the chain has to be read, and the result is cached briefly so a second request for the same transaction is instant. Nothing is tied to you, and the finished document is assembled in your browser.

Can I use it for accounting or a tax return?

It is built for it: the amounts carry the price at the time of the transaction rather than today's, which is the figure a return asks for. It is a record of what the chain says, not advice about how to treat it.

Why is the text selectable instead of an image?

Because a receipt you cannot copy a hash out of is half a receipt. The page is drawn as text, so it stays sharp when printed and can be searched afterwards.