# getTransactionCount

> Returns the total number of transactions ever processed by the cluster.

Source: https://docs.constant-k.com/rpc/http/gettransactioncount/

`getTransactionCount` returns the total number of transactions the cluster has processed since genesis, as tracked by the bank at the requested commitment level.

It has no relationship to a specific account's history; `getSignaturesForAddress` covers that instead.

- Transport: HTTP, JSON-RPC 2.0 `POST` to `https://rpc-newyork.constant-k.com/?api-key=YOUR_API_KEY` (New York) or `https://rpc-frankfurt.constant-k.com/?api-key=YOUR_API_KEY` (Frankfurt) or `https://rpc-amsterdam.constant-k.com/?api-key=YOUR_API_KEY` (Amsterdam). The key also works as an `x-api-key` header.
- Category: Transactions
- Availability: All plans
- Rate limits: Free 5/s · Operator 50/s · Blade Runner 200/s · Nexus 500/s

## Parameters

`params` is a positional JSON array, in this order:

- `config` (object, optional): Optional configuration.
  - `commitment` (string, optional, one of `finalized`, `confirmed`, `processed`, default `"finalized"`): Bank state to read the counter from.
  - `minContextSlot` (integer, optional): Minimum slot the node must have processed before answering.

## Result

- `result` (integer, optional): Total transaction count. A plain integer, not wrapped in a context/value envelope.

## Example: Get the cluster's total transaction count

Request:

```bash
curl "https://rpc-newyork.constant-k.com/?api-key=YOUR_API_KEY" \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "getTransactionCount",
    "params": []
  }'
```

Response:

```json
{
  "jsonrpc": "2.0",
  "result": 549621887074,
  "id": 1
}
```

## Notes

- This number only increases; it is a smoke test for whether the node's bank is advancing, not a signal about any specific account or program.