> For the complete documentation index, see [llms.txt](https://docs.megaeth.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.megaeth.com/developer-docs/rpc/reference/debug_gethistorytransactioncount.md).

# debug\_getHistoryTransactionCount

## Summary

Returns the chain-wide cumulative transaction count up to and including a given block.

The public MegaETH endpoint supports this method. The standard, node, and gateway layers below identify behavior that differs from a generic Ethereum endpoint.

## Parameters

**`block`** string **REQUIRED**

Hex block number or tag (`earliest`, `latest`, `safe`, `finalized`). `pending` is not supported.

## Result

**`result`** Quantity

Cumulative transaction count across all blocks up to the selected block. Consecutive blocks with no transactions return the same value.

## Comparison with Ethereum Standard JSON-RPC

### Ethereum Standard

`debug_getHistoryTransactionCount` is not part of the core Ethereum execution JSON-RPC API. It is a MegaETH debug extension.

### MegaETH Node Behavior

MegaETH adds this diagnostic method. It resolves the selected block and returns the cumulative transaction count through that block; `pending` is not a supported selector.

### MegaETH Public Gateway

The public gateway exposes the method in the simple read tier and caches resolved results as immutable data for 30 minutes.

## Errors

The `| Scope |` column distinguishes method failures from gateway policy errors.

| Code     | Scope            | Message             | When it happens                                                                 |
| -------- | ---------------- | ------------------- | ------------------------------------------------------------------------------- |
| `-32001` | Method           | Resource not found  | Block selector cannot be resolved or unsupported tag such as `pending` was used |
| `-32602` | Request          | Invalid params      | Invalid parameter shape                                                         |
| `-32005` | Transport/policy | Rate limit exceeded | The caller exceeds the public gateway's simple read budget.                     |
| `-32099` | Transport/policy | Payload too large   | The request body exceeds the 128 KiB public endpoint limit.                     |

See also [Error Codes](/developer-docs/rpc/error-codes.md).

## Examples

Endpoint: `https://mainnet.megaeth.com/rpc`

Capture date: July 24, 2026

Outcome: success

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "debug_getHistoryTransactionCount",
  "params": ["0x12a05f"]
}
```

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

## Sources

* Spec: EIP-1474 for JSON-RPC framing and error conventions; this method is an extension or legacy compatibility method.
* Code: `git@github.com:megaeth-labs/mega-reth.git @ ab60376631228edab3a6df180f295280bad26e93: crates/megaeth/rpc/src/debug.rs`
* Code: `git@github.com:megaeth-labs/mega-rpc.git @ 06aa35aa95d569c227cc25d2aa12834eb0458aa0: workers/src/spec/methods.ts`
* Probe: MegaETH Mainnet public endpoint, July 24, 2026


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.megaeth.com/developer-docs/rpc/reference/debug_gethistorytransactioncount.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.