getBlock

getBlock returns the contents of a confirmed block at a given slot: its blockhash, the parent slot it builds on, the block height and block time, and — depending on the config you pass — the full list of transactions, just their account keys, just their signatures, or none of them.

Use it to inspect or index ledger history: replay the transactions in a block, correlate on-chain activity to a wall-clock time via blockTime, or walk the chain by following parentSlot. Because a fully-detailed block can be large, shape the response with transactionDetails and rewards to fetch only what you need.

Not every slot produces a block (slots can be skipped). If you request a slot that was skipped or is not available in the node's ledger, the call returns a JSON-RPC error rather than an empty result — see Errors.

JSON-RPC params is a positional array: [slot, config?].

The example uses transactionDetails: "signatures", so transactions is omitted and the block's transaction signatures are returned in signatures instead.

With the default transactionDetails: "full", the response instead carries a transactions array — each entry an object with transaction (encoded per encoding) and meta (fee, balances, logs, status) — and signatures is omitted.

Errors are returned in the standard JSON-RPC error envelope. See the shared errors reference for the full envelope shape and shared codes.

JavaScript (fetch)

const res = await fetch("https://api.triport.io/v1/sol", {
  method: "POST",
  headers: {
    "Authorization": `Bearer ${process.env.TRIPORT_API_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    jsonrpc: "2.0",
    id: 1,
    method: "getBlock",
    params: [
      348392040,
      { transactionDetails: "signatures", rewards: false, maxSupportedTransactionVersion: 0 },
    ],
  }),
});


const { result } = await res.json();
console.log(`Block ${result.blockHeight} @ slot ${result.parentSlot + 1}`);
console.log(`Produced at ${new Date(result.blockTime * 1000).toISOString()}`);
console.log(`${result.signatures.length} transactions`);

TypeScript SDK (@triport/sdk)

import { TriportClient } from "@triport/sdk";


const client = new TriportClient({ apiKey: process.env.TRIPORT_API_KEY });


const block = await client.solana.getBlock(348392040, {
  transactionDetails: "signatures",
  rewards: false,
  maxSupportedTransactionVersion: 0,
  commitment: "finalized",
});


console.log(`Blockhash ${block.blockhash}, ${block.signatures.length} txs`);

Python (triport-sdk)

import os
from datetime import datetime, timezone
from triport import TriportClient


client = TriportClient(api_key=os.environ["TRIPORT_API_KEY"])


block = client.solana.get_block(
    348392040,
    transaction_details="signatures",
    rewards=False,
    max_supported_transaction_version=0,
    commitment="finalized",
)


produced = datetime.fromtimestamp(block["blockTime"], tz=timezone.utc)
print(f"Block height {block['blockHeight']} produced at {produced.isoformat()}")
print(f"{len(block['signatures'])} transactions")

• processed is not a valid commitment here — use confirmed or finalized. Passing processed yields an invalid-params error.
• Skipped slots: not every slot produces a block. Requesting a skipped slot returns a slot-skipped error (-32007 / -32009), not an empty block — handle it as expected for sparse ranges.
• Versioned transactions: if a block contains v0 transactions and you omit maxSupportedTransactionVersion, the request fails. Set it to 0 to receive versioned transactions alongside legacy ones.
• Shape the payload: full blocks can be large. Use transactionDetails: "signatures" or "none" and rewards: false to keep responses small when you only need a summary.
• Related methods: use getBlocks / getBlockTime to discover and time slots, getBlockHeight for the current height, and getSlot for the slot the cluster has reached.