跳转到主要内容

Overview

Transaction monitoring lets you watch Solana transactions as they happen. Track swaps, transfers, success/failures, program calls, and token changes - all in real-time.
You’ll need: Run npm install @triton-one/yellowstone-grpc first

Installation

Complete Working Example

Here’s a ready-to-use transaction monitor that you can customize:

How to Filter Transactions

Watch transactions using specific programs:

More Examples

Example 2: Track Failed Transactions

Find out why transactions fail:

Example 3: Watch Big Transfers

Track large SOL transfers:

Understanding Filters

Include (OR)

accountInclude: Transaction must touch ANY of these accounts

Required (AND)

accountRequired: Transaction must touch ALL of these accounts

Exclude (NOT)

accountExclude: Transaction must NOT touch any of these

How They Work Together

Transaction passes if: (include OR empty) AND (all required) AND NOT (any excluded)

What You Can Build

Monitor DEX transactions to find trading opportunities, track competitors, or analyze market activity in real-time.
Watch specific wallets or programs to see every transaction they make. Perfect for portfolio tracking or whale watching.
Track failed transactions to debug your program, understand user issues, or monitor network problems.
Measure transaction volume, fees, and activity across programs to understand usage patterns and trends.
Get instant notifications for high-value transfers, specific program calls, or suspicious activity.

Tips for Better Performance

Pick Right Commitment

CONFIRMED is usually best - fast but reliable

Filter Smart

Use specific program IDs to reduce data

Process Async

Don’t block - handle transactions asynchronously

Watch Resources

Monitor your memory and CPU usage

Common Questions

It depends on your filters. Watching all transactions = huge data. Watching one program = manageable. Watching a specific wallet = very little. Always use filters!
Yes! Just add them all to accountInclude. The transaction will match if it touches ANY of them.
  • Include (OR): Transaction touches ANY of these accounts
  • Required (AND): Transaction touches ALL of these accounts
Use Include for “I want to see transactions involving A or B or C” Use Required for “I only want transactions that involve both A and B”
Usually no - they’re just noise. But set failed: true if you’re debugging or analyzing failure patterns.
Add the wallet address to accountInclude. You’ll see every transaction that touches that wallet.
Set vote: false in your filter. Vote transactions are validator consensus votes and usually aren’t what you want.
Compute units measure how much computation a transaction used. More complex transactions use more compute units and usually cost more.

Next Steps

Account Monitoring

Also watch account changes

Real Example: Pump.fun

See transaction parsing in action

Best Practices

Optimize your setup

Quickstart

Get started fast