Portal
This document provides a technical overview of the Nexera Portal, an analytics dashboard designed for real-time monitoring of a Nexera node's transaction pool (mempool).
The portal visualizes metrics scraped by a Prometheus instance, offering node operators and network analysts critical insights into transaction flow, network health, and node performance.
Transaction Pool Metrics
The following metrics provide a detailed view of the state and activity within the node's mempool.
| Metric | Description |
|---|---|
| Total Transactions in Pool | A real-time counter of all transactions currently held within the node's mempool (pending, basefee, and queued). It serves as a primary indicator of the immediate load on the node. |
| Mempool Usage vs Configured Limit | A visualization (gauge or graph) of the current mempool size as a percentage of the node's configured limit. This is a critical health metric; approaching 100% signals congestion and potential transaction eviction. |
| Pending Transactions | The number of transactions eligible for inclusion in the next block. These have a valid nonce and a maxFeePerGas sufficient to cover the current basefee. This represents the set of "ready-to-go" transactions. |
| Basefee Transactions | A subset of the pending pool, this counts transactions whose maxFeePerGas is sufficient for the basefee but may have a low priority fee (tip), differentiating them from transactions stuck due to low fees. |
| Queued Transactions | The number of transactions with a non-sequential nonce that are held but cannot be processed until the preceding transactions are confirmed. A high count can indicate large batch submissions. |
| Blob Transactions | A count of transactions that include data "blobs" (per EIP-4844), primarily used by Layer 2 rollups. This is a direct indicator of L2 activity and its demand on the data availability layer. |
| Pending Size | The total size, in bytes or kilobytes, of all transactions in the pending pool. This measures the memory footprint of immediately processable transactions. |
| Basefee Size | The total size, in bytes or kilobytes, of all transactions in the basefee pool. This helps in understanding the memory allocation for eligible but not yet prioritized transactions. |
| Queued Size | The total size, in bytes or kilobytes, of all transactions in the queued pool. This is used to monitor the memory resources being held for future-dated transactions. |
| Blob Size | The total size, in bytes or megabytes, of the data blobs attached to all blob-carrying transactions in the mempool. This is critical for monitoring the demand on the dedicated blob data market. |
| Invalid Transactions Rate | A time-series graph showing the rate at which the node discards invalid transactions (e.g., bad signature, insufficient funds). A sudden spike can indicate a misconfigured peer, a bug, or a potential DoS attack. |
| Evicted Transactions Rate | A time-series graph showing the rate at which transactions are dropped from the mempool, either because the pool is full or the network basefee rose above the transaction's maxFeePerGas. This is a direct measure of network congestion. |