Skip to main content
Filter executed transactions by the accounts they reference. Use the execution metadata for fees, logs, errors, and token balances; decode instructions or events for program-specific trade details. Save the quickstart helper as stream.mts in the same directory. These examples use the same environment variables and dependencies.

Subscribe by program or account

transactions.mts

Combine transaction filters

  • accountInclude: match at least one listed account.
  • accountRequired: require every listed account.
  • accountExclude: reject transactions that reference any listed account.
  • vote: false: exclude validator votes.
  • failed: false: successful executions only. Use true for failures, or omit it for both.
  • signature: select one transaction signature.
The include, required, and exclude conditions work together. An empty include list does not restrict the set by itself.

Interpret the result

The signature is binary; convert it with base58. The slot is on update.transaction, while execution details are on update.transaction.transaction.meta. A balance difference can include fees, rent, or several instructions, so it is not automatically a transfer amount.

Track duplicates and gaps

For confirmed or finalized transaction indexing, use the signature as a deduplication key. If you consume processed updates, retain slot/fork context so later confirmation can reconcile provisional results. A reconnect does not by itself recover missed history.

Pump.fun trades

Reliability and performance