Learn · Updated November 18, 2026

Why the first signature is a Solana transaction's ID

A Solana transaction signature identifies the transaction: the first of its signatures, which belongs to the fee payer, is the transaction ID that explorers and RPC methods look it up by. It is 64 bytes, usually shown in base58. On the confirmed chain a signature appears once, which makes it a natural primary key.

Where the signature sits in the bytes#

In a legacy or v0 transaction the signatures come first: a compact-u16 count, then 64 bytes per signature, then the message they sign. The ID is the first 64 bytes after the count. In a v1 transaction the signatures come last, after the message, so the ID is the first 64 bytes of the signature block at the end.

That difference is the most common way a decoder records wrong IDs. Code that always takes the 64 bytes after the first byte reads part of a v1 message instead of a signature, and nothing fails loudly: you get a plausible-looking string that matches no transaction. What is inside a Solana transaction and the v1 format show both layouts.

Base58 form#

People see the ID as base58 text, usually 87 or 88 characters for 64 bytes. Base58 is for display and for RPC calls; it costs work to produce and compare. Inside a pipeline you can keep the 64 raw bytes as the key and convert only at the edges, where you talk to RPC or show a row to a person. Base58 and public keys covers the encoding and its cost.

Using it as a key#

Three properties make the first signature a good primary key. It exists before the transaction runs, so a row can be keyed the moment you decode it from shreds. It is the same value RPC uses, so you can later look the transaction up by it. And the network refuses to process the same transaction twice: each validator keeps a status cache of recently processed messages, and a repeat is rejected with AlreadyProcessed while its blockhash is still valid. After that, the blockhash itself has expired and the transaction cannot be processed at all.

So on the confirmed chain, one signature means one transaction in one block.

When the same signature shows up twice#

Uniqueness holds for the confirmed chain, not for everything a pipeline sees.

SituationWhy the signature repeatsWhat to do
The same shred arrives twicethe network or your capture duplicated a packetdedupe shreds by slot and index before decoding
The transaction appears in two slotsit was in a block that was later skipped and then landed in anotherkeep both sightings provisional; reconciliation keeps the one that confirmed
Your process restarts and replaysyou decoded the same data againmake writes idempotent on the signature
Two feeds or retries deliver itseveral sources see the same transactiondedupe on the signature at the merge point

None of these is two different transactions sharing an ID; they are one transaction seen more than once.

Keying shred-decoded rows by signature#

From shreds you get the signature immediately, but not the outcome. Key the row by signature, store the slot you saw it in as an attribute rather than part of the key, and let a later step settle the status. If you key on slot and signature together, the skipped-slot case above creates two rows for one transaction and someone has to merge them later. Deduplicating transactions and reconciling with RPC are the two steps that keep the key honest.

Questions about transaction signatures#

Is the transaction ID the same as the transaction hash?#

Solana identifies transactions by the first signature, not by a hash of the transaction. Validators do hash the message internally for duplicate detection, but that hash is not the public ID.

Can two different transactions have the same first signature?#

The first signature is the fee payer's signature over that exact message, so a different message gives a different signature. A repeat of the same signature means the same transaction.

Does a failed transaction have a signature?#

Yes. A transaction that landed and failed still has its ID, still paid its fee and is still in the block.

What a signature does not tell you#

The ID says nothing about outcome or finality. Seeing a signature in shreds means a leader included the transaction in block data, not that the block survived or the transaction succeeded. Until you reconcile, a signature-keyed row is a claim about what was sent, not about what happened.

Putting the key to work#

Idempotent writes builds a table around this key, and blockhash expiry explains the window in which a repeat is still possible. For the decoder that extracts the ID correctly from all three formats, see the Rust decoder, and to key your own rows from live shreds, start with a first decode.

Sources#

Raw shreds on your own server

Ultra Low Latency Shreds is $200 and Standard Shreds is $100. You pay in crypto, tell us which IPv4 address and UDP port should receive the stream, and we wire it up by hand.