Antminer X9
Monero ASIC Miner
1000KH
HASHRATE
2.47W/KH
EFFICIENCY
2470W
POWER
£874.51
EST. MONTHLY
202
DAYS
EST. ROI
This guide explains Bitcoin Core listtransactions RPC in plain English. It shows what the command does, what its result means and what it cannot prove.
TL;DR
- What it is: Bitcoin Core 0.16.0 listtransactions returned recent wallet accounting entries using deprecated account selection, count, skip and watch-only options. The account argument should be an asterisk for all accounts.
- Why it matters: listtransactions is a recent wallet-accounting view, not a stable transaction ledger. Reliable consumers understand move entries, row multiplicity and changing pagination and reconcile against transaction and chain state.
- Current position: Bitcoin Core 0.16.0 listtransactions returned recent wallet accounting entries using deprecated account selection, count, skip and watch-only options.
Bitcoin Core listtransactions RPC in simple English
Bitcoin Core listtransactions RPC: One Bitcoin transaction may create multiple send, receive, fee or self-transfer entries. Do not count array rows as unique transactions.
Simple example
A miner is checking Bitcoin Core listtransactions RPC. Group carefully by txid and vout while preserving wallet-specific category and fee effects. Use the asterisk to request all accounts and treat account fields as legacy bookkeeping.
Key terms in plain English
- BIP:
- Bitcoin Improvement Proposal: a document describing a proposed rule, standard or process. Its status must be checked separately.
- Bitcoin Core:
- Widely used software that validates Bitcoin and can provide wallet, network and operator tools.
- RPC:
- A command that software sends to a node to request information or a local action.
- Mempool:
- A node’s changing local collection of valid, unconfirmed transactions.
- Node:
- A computer running Bitcoin software that checks data and communicates with other peers.
Deprecated account filter
Use the asterisk to request all accounts and treat account fields as legacy bookkeeping. A move category is local account accounting with no address, txid or block, and must never be represented as an on-chain payment.
Count and skip
count defaults ten and skip defaults zero from the most recent records. Validate non-negative bounds. Because new events shift positions, repeated pages can duplicate or omit entries; overlap queries and deduplicate using stable event identity.
Entry versus transaction
One Bitcoin transaction may create multiple send, receive, fee or self-transfer entries. Do not count array rows as unique transactions. Group carefully by txid and vout while preserving wallet-specific category and fee effects.
Signs and optional fields
Send and outbound move amounts are negative; receive and inbound move amounts positive. Fee is negative for sends. Block, txid and address fields are absent for moves and conditional elsewhere. Parse by category rather than assuming a uniform schema.
Trust and replacement
trusted describes whether unconfirmed outputs are considered safe to spend under wallet policy. BIP125 status may be yes, no or unknown; abandoned applies to sends. None is irreversible settlement, and chain or mempool state can change.
Watch-only and privacy
include_watchonly broadens results to monitored scripts without spending keys. Account, address, comments, otheraccount and labels are sensitive. Restrict access and separate watch-only state in downstream reports.
How specialists test it
Operators test the command on a non-production node first. They check a normal reply, an invalid request, a timeout and a restart. This shows what the response means and prevents one local result from being mistaken for a network-wide outcome.
Frequently asked questions
What is the main point of Bitcoin Core listtransactions RPC?
Bitcoin Core listtransactions RPC: One Bitcoin transaction may create multiple send, receive, fee or self-transfer entries.
For Bitcoin Core listtransactions RPC, what should a beginner know about deprecated account filter?
Use the asterisk to request all accounts and treat account fields as legacy bookkeeping.
For Bitcoin Core listtransactions RPC, what should a beginner know about count and skip?
count defaults ten and skip defaults zero from the most recent records.
For Bitcoin Core listtransactions RPC, what should a beginner know about entry versus transaction?
One Bitcoin transaction may create multiple send, receive, fee or self-transfer entries.
Conclusion
listtransactions is a recent wallet-accounting view, not a stable transaction ledger. Reliable consumers understand move entries, row multiplicity and changing pagination and reconcile against transaction and chain state.
Primary sources
Check the current specification status and the documentation for the exact implementation you operate before moving production funds or changing a mining node.
Join the ASIC Mining Discussion
Members can read and join the discussion
Log in to read comments from other miners. Create a free account if you would like to ask a question or share your experience.
Membership helps us protect the discussion from spam and keep answers useful.