Overview
Entries are the smallest building blocks of the Solana blockchain. Think of them as containers that hold groups of transactions.Start here first: Complete the Quickstart Guide to set up your stream manager.
What are Entries?
- The Basics
- What's Inside
- When to Use This
Entries are transaction containersHere’s what they do:
- Bundle transactions: They group transactions together
- Set the order: Transactions run in a specific order
- Link together: Each entry connects to the next one
- Track time: They record when things happen
Real Examples
Example 1: Basic Entry Monitor
Watch entries as they come in:Example 2: Filter Entries
Only process entries you care about:Entry Data Structure
Entry Fields
Entry Fields
How Entries Compare
How Entries Compare
Entries vs Transactions:
- Entries = groups of transactions
- Shows you the order things happen
- Includes timing proof data
- Blocks = many entries combined
- Entries = smaller pieces inside blocks
- Blocks show finality
- Slots = 400ms time windows
- One slot = multiple entries
- Entries = what happened in that time
Performance Considerations
Lots of Data
This stream is busy
- Many messages per second
- Never stops during network activity
- Each entry has multiple transactions
- You need fast processing
Stay Fast
Keep your code efficient
- Don’t wait for each entry (use async)
- Process multiple entries at once
- Only look at what you need
- Sample the data if analyzing a lot
Common Use Cases
- Performance Research
- Validator Research
- Network Debugging
Study how fast things workTrack how the network groups transactions. Find patterns that show problems or ways to make things faster.
Filtering Tips
Entry monitoring sends you ALL entries. There’s no built-in filtering. Here’s how to deal with that:Ways to handle the data:
- Filter in your code: Only process what you care about
- Sample it: Look at every 10th or 100th entry for stats
- Time windows: Only look at specific time periods
- Slot filtering: Only process certain slots
- Transaction types: Focus on specific transaction types (see Example 3)
Best Practices
When to Use This
When to Use This
Use entry monitoring for:
- Deep blockchain research
- Studying validators
- Debugging network issues
- Academic projects
- Understanding Proof of History
- Normal apps
- User interfaces
- Business features
- Trading apps
Handle the Data
Handle the Data
Tips for processing:
- Build fast code
- Don’t wait for each entry (use async)
- Sample if you’re analyzing a lot
- Watch your memory usage
- Handle when data comes too fast
Analysis Tips
Analysis Tips
Do good analysis:
- Pick specific things to measure
- Use sampling for large datasets
- Calculate rolling averages
- Look at patterns over time
- Compare with other data sources
Troubleshooting
Too Much Data
Too Much Data
Problem: The entry stream is overwhelmingFix it:
- Filter in your code (see Example 3)
- Sample the data
- Use async processing
- Check your system resources
- Consider transaction monitoring instead
Need More Info
Need More Info
Problem: Entries don’t have enough contextFix it:
- Also monitor transactions
- Check account updates
- Use block monitoring too
- Keep your own state
Common Questions
Why are there so many entries?
Why are there so many entries?
Entries are created constantly as validators process transactions. The Solana network is very active, so you’ll see many entries per second. Use filtering to manage the volume.
What are empty entries?
What are empty entries?
Empty entries are part of Solana’s Proof of History mechanism. They help maintain timing even when there are no transactions to process. They’re normal and expected.
Should I filter out vote transactions?
Should I filter out vote transactions?
Usually yes. Vote transactions are validator consensus votes and typically aren’t relevant for application-level monitoring. See Example 3 for how to filter them.
How do I know if I'm processing too slowly?
How do I know if I'm processing too slowly?
If you’re falling behind, you’ll see increasing delays between entry creation and processing. Monitor your processing time and queue sizes. Consider sampling or better filtering if you can’t keep up.
Next Steps
Pump.fun Example
See a real example
Transaction Monitoring
Monitor transactions instead
Slot & Block Monitoring
Higher-level monitoring
Best Practices
Optimize your setup
Remember: Entry monitoring is for advanced research. Most apps work better with transaction, account, or block monitoring.