No deshredding pipeline to operate
Skip packet handling, reconstruction, and transaction extraction work. Shreder does the heavy lifting so your team can focus on application logic.
// Decoded Shreds
Decoded Solana shreds without running your own decoder
Subscribe to low-latency Solana transaction data extracted from shreds, with account filters and no raw deshredding infrastructure to maintain.
- Transaction data extracted from Solana shreds
- Geyser-style account filters
- No local deshredder required
- Lower operational overhead than Raw Shreds
- Available across Shreder’s global regions
Decoded Shreds is ideal when you want early transaction data and simple filters. Choose Raw Shreds for packet-level control, Binary for even lower latency, or Fastlane/Geyser for post-execution state.
Formatdecoded transaction gRPC stream
Best forfast transaction datawithout a raw decoder
Filtersaccount_includeaccount_excludeaccount_required
Regionsfrankfurt, amsterdam,london, tokyo,new york
For public performance data, see Shreder’s shred-stream benchmarks. View benchmarks →
// Overview
What are Decoded Shreds?
Solana block data begins moving through the network as shreds before many downstream systems expose full processed updates. Raw shreds are powerful, but expensive to operate well: your team must receive packets, deduplicate, reconstruct entries, decode transactions, filter, and route the result.
Decoded Shreds moves that work into Shreder’s low-latency infrastructure. Instead of receiving raw UDP packets, your application subscribes to a decoded transaction stream with account filters.
- Shreder handles shred collection and decoding.
- You subscribe to transaction updates through a gRPC interface.
- You can filter by included, excluded, or required accounts.
- You receive transaction-level data earlier than any post-processed paths.
- You avoid running and tuning a local raw deshredding pipeline.
Decoded Shreds is a pre-execution transaction stream for early intent detection. It does not include post-execution account state, logs, balances, or final outcomes. Use Geyser gRPC / Fastlane when you need that context.
// Why Decoded Shreds
Shred-level signal without decoder-level maintenance
Decoded Shreds removes the most operationally complex part of the raw path while keeping your application close to the data source.
Simple account filters
Subscribe only to relevant transactions using include, exclude, and required account filters.
Close to the shred frontier
Built from shred streams instead of waiting for Geyser updates.
Practical production path
For many teams, this is the right balance of speed, convenience, and operational cost.
// Use cases
Built for teams that need early transaction data, not decoder maintenance
Decoded Shreds is the right starting point when your application needs low-latency transaction visibility without raw shred reconstruction overhead.
Trading systems
Monitor specific markets, programs, or accounts and react to transaction intent without running a local deshredder.
Searchers
Subscribe to filtered transaction streams for target accounts and route matches into opportunity-detection logic.
DeFi and wallets
Track relevant program activity early, then pair with post-execution streams when users need final status.
Indexers and analytics
Use Decoded Shreds as an early transaction source, then reconcile with Fastlane, Geyser, or RPC for full execution metadata.
For even lower latency consider using Binary.
// Benchmarks
Decoded Shreds Benchmarks
We benchmarked Decoded Shreds against other shred-stream providers in the same region and setup. Decoded Shreds delivered the first actionable signal in the vast majority of cases—without the operational overhead of running your own decoder.
Run 001
Shreder vs Jito shred streaming
Measured in Frankfurt, Teraswitch FRA2.
| Provider | p50 | p95 | p99 |
|---|---|---|---|
| Shreder.xyz Frankfurt | 0.00 ms | 0.00 ms | 0.00 ms |
| Jito Frankfurt | 4.61 ms | 38.51 ms | 51.12 ms |
// How it works
How Decoded Shreds stream works
01
Solana activity is propagated as shreds
Before the downstream APIs expose a transaction, Solana block data is already moving through the network as shreds.
02
Shreder receives and reconstructs the stream
Shreder infrastructure receives shreds in low-latency regions, reconstructs transaction data, and prepares updates for subscriptions.
03
Your filters select relevant transactions
Your client sends include/exclude/required account rules and Shreder matches updates server-side.
04
Your app receives decoded updates
Matching transactions stream to your service. You can also confirm outcomes with Fastlane/Geyser when needed.
// Filters and format
Subscribe to the transactions that matter
Decoded Shreds supports account-based transaction filters so your hot path receives less noise before business logic.
account_include
Match transactions involving any account in the include list.
account_exclude
Ignore transactions involving any account in the exclude list.
account_required
Match transactions that include all required accounts.
// decoded-shreds · filter map
{
"pumpfun": {
"account_include": [],
"account_exclude": [],
"account_required": [
"6EF8rrecthR5Dkzon8Nwu78hRvfCKubJ14M5uBEwF6P"
]
}
}// Performance
Measure time-to-actionable transaction, not just time-to-packet
For production systems, the useful latency metric is when a transaction becomes actionable in your app.
Actionable latency
- Shred propagation
- Reconstruction and decoding
- Filter matching
- Stream delivery
- Client receive
- Application routing
A raw feed may reach your server earlier, but if your local decoder/filter path is slower than a managed decoded stream, raw can lose the end-to-end race.
Use public benchmarks as a starting point, then run controlled tests from your production region and hardware profile. View shred stream benchmarks →
// Benchmarking
How to measure Decoded Shreds performance
Use an open-source benchmark to measure Decoded Shreds latency in your current setup and compare it side by side with other providers.
GeyserBench is an open-source tool for realistic benchmarking from your own environment. It lets you run the same monitored accounts and filters against multiple endpoints and compare results under your actual network path and hardware profile.
The output helps you validate first-detection share and latency deltas (p50/p95/p99) for your current production setup, so you can decide whether Decoded Shreds improves your real time-to-actionable signal.
// Compare
Choose the right Data stream
Decoded Shreds is the practical starting point for many teams because it combines shred-level delivery with transaction-level ergonomics.
| Product | Format | Best for | Customer-side work | Latency profile |
|---|---|---|---|---|
| Raw Shreds | Raw UDP shred packets | Teams with custom deshredding and strict latency budgets | Highest: receive, dedupe, reconstruct, decode, filter | Earliest feed; end-to-end speed depends on your decoder |
| Decoded Shreds | Structured transaction stream with filters | Production teams that want shred-level delivery without running a decoder | Low: subscribe and process transaction updates | Low latency with less operational overhead |
| Binary | Transaction data from shreds | Trading systems that want efficient transaction-level delivery | Low: no local decoding required | Lowest-latency transaction-level path for most workloads |
| Geyser gRPC / Fastlane | Yellowstone-compatible gRPC | Existing Geyser users, indexers, wallets, DeFi apps | Low: use existing gRPC tooling | Same interface; Fastlane is optimized for speed |
Decoded Shreds is pre-execution transaction data. For account state, logs, balances, and execution results, use Geyser gRPC or Fastlane.
Not sure which stream to use? Talk to Shreder →
// Requirements
Technical requirements
Decoded Shreds is simple to integrate, but production systems should still handle stream lifecycle, reconnection, and backpressure.
- A Shreder endpoint in your selected region.
- Transaction filters for target accounts or programs.
- Optional confirmation path through Fastlane, Geyser, or RPC.
- Reconnect logic.
- Backpressure handling.
Decoded Shreds FAQ
What are Decoded Shreds?
Decoded Shreds delivers transaction-level data extracted from Solana shreds while Shreder handles low-level reconstruction and decoding.
How is Decoded Shreds different from Raw Shreds?
Raw Shreds delivers unprocessed UDP packets and requires your own deshredding stack. Decoded Shreds moves that work into Shreder and streams transaction updates directly.
How is Decoded Shreds different from Binary?
Decoded Shreds returns structured transaction updates. Binary returns serialized transaction payloads that you deserialize locally. Both provide decoded transaction data, however Binary gives further latency improvements. Consider using Binary for workloads with even stricter latency requirements.
Is Decoded Shreds the same as Geyser gRPC?
No. Decoded Shreds is part of Shred Streams and focuses on early pre-execution transaction data. Fastlane/Geyser is for Yellowstone-compatible post-execution workflows.
Does Decoded Shreds include account state, logs, balances, or execution results?
No. For post-execution context, use Fastlane or Geyser gRPC.
Do I need to run my own validator or decoder?
No. Decoded Shreds is built for teams that want early transaction data without operating a raw decoder pipeline.
What filters are supported?
account_include, account_exclude, and account_required.
Can I subscribe to multiple filters at once?
Yes, you can set up multiple filters and multiple connections.
What regions are available?
Frankfurt, Amsterdam, New York, London, and Tokyo.
How should I benchmark Decoded Shreds?
Use GeyserBench to compare Decoded Shreds with other providers in your region and setup. See the Benchmarks page.
When should I choose Raw Shreds instead?
Choose Raw Shreds when you need packet-level control and are ready to run a high-performance deshredding pipeline.
How do I get access?
Start from the Shreder console or contact the team. We will provide endpoint and region guidance.
Start streaming decoded Solana transactions
Tell us your target region, accounts or programs to monitor, current provider, and latency goals. We will help you configure Decoded Shreds and benchmark it against your setup.