Mempool Operations
resource: mempool — unconfirmed-transaction visibility
getInfo
Returns aggregate mempool statistics — no parameters beyond network.
| Field | Type | Required | Description |
|---|---|---|---|
network | select | No | Defaults to Bitcoin:DefaultNetwork. |
Example response:
{
"count": 84213,
"vsizeBytes": 41250880,
"totalFeeSats": 218400000
}| Response Field | Meaning |
|---|---|
count | Number of unconfirmed transactions currently in the mempool. |
vsizeBytes | Total virtual size of all mempool transactions. |
totalFeeSats | Sum of fees (satoshis) across all mempool transactions. |
getTransactionIds
Returns the raw list of txids currently sitting unconfirmed in the mempool.
| Field | Type | Required | Description |
|---|---|---|---|
network | select | No | Defaults to Bitcoin:DefaultNetwork. |
getRecent
Returns the most recently-added mempool transactions with more detail than a bare txid list.
| Field | Type | Required | Description |
|---|---|---|---|
network | select | No | Defaults to Bitcoin:DefaultNetwork. |
Why check the mempool at all? A transaction can sit unconfirmed for minutes to hours
depending on its fee rate relative to current network demand. Use
mempool/getInfo alongside
fee/getEstimates to judge whether a pending payment is likely to
confirm soon, or address/getTransactionsMempool to watch a
specific address for incoming unconfirmed payments.