Read Solana entry metadata with Yellowstone gRPC - Solana Tracker

The entry stream exposes Proof of History entry metadata: hashes, indexes, and transaction counts. It does not contain transaction bodies, execution logs, or per-transaction success flags. Save the quickstart helper as stream.mts in the same directory. These examples use the same environment variables and dependencies.

entries.mts

import { subscribe } from "./stream.mts";

for await (const update of subscribe({ entry: { entries: {} } })) {
  const entry = update.entry;
  if (!entry) continue;
  console.log({
    slot: entry.slot,
    index: entry.index,
    hash: Buffer.from(entry.hash).toString("hex"),
    numHashes: entry.numHashes,
    transactionCount: entry.executedTransactionCount,
    startingTransactionIndex: entry.startingTransactionIndex,
  });
}

npx tsx entries.mts

Read entry fields

slot and index locate the entry within a slot.
hash is binary; the example displays it as hex.
numHashes records the hash count for the entry.
executedTransactionCount is a count, not a transaction array.
startingTransactionIndex locates its first transaction within the block.

Keep 64-bit values as strings or BigInt. A zero transaction count is valid.

Filter and correlate

The entry filter has no account or program fields. Filter by slot or sample updates in your consumer. For instruction parsing, vote filtering, or execution results, join transaction or block data by slot and transaction index. Do not infer those details from entry counts.

Transactions

Slots and blocks