Andreas Node #1
Standard 300 MB mempool
Transactions–
Virtual size–
Usage / Max–
Mempool min fee–
Min relay fee–
Incremental relay–
Bitcoin Core –Waiting for data
Tools · Server query
Mempool Acceptance Test
Compare whether the Andreas and Adam Bitcoin Core nodes would accept a signed raw transaction into their different mempools right now. The check covers transaction structure, consensus validity, current chain state, fees, conflicts, and each node’s active relay policy.
The test is read-only: it does not broadcast the transaction, announce it to peers, store it for later, or guarantee that either node will accept it at a later time.
Explicit server query
Submission is explicit and read-only.
Submitted input: The full signed raw transaction is sent only after you explicitly submit it. Network effect: BitcoinStats sends it to the selected BitcoinStats-operated node or nodes for a read-only mempool policy check. It is not broadcast or stored. First-party cached node metrics refresh every 10 seconds while the page is visible.
Raw signed transactionBitcoinStatsSelected node(s)Per-node results
First-party node metrics refresh every 10 seconds while this tab is visible. Your transaction is submitted only when you press “Test acceptance”; it is never retried automatically or stored in the URL, browser storage, or analytics.
Current node mempools
Two nodes, two independent policy views
The live values below come from existing BitcoinStats node caches. Andreas uses Bitcoin Core’s standard 300 MB mempool size; Adam has an expanded 1 GB mempool and may retain low-fee transactions longer during sustained pressure.
See Node Details for each node’s role, platform, hardware, operating system, connectivity, and live operational data.
Adam Node #4
Expanded 1 GB mempool
Transactions–
Virtual size–
Usage / Max–
Mempool min fee–
Min relay fee–
Incremental relay–
Bitcoin Core –Waiting for data
Mempool min fee is the node’s current admission floor. A fee rate above it is necessary when the floor is elevated, but it does not guarantee acceptance: inputs, conflicts, scripts, standardness, and ancestor or descendant limits are checked separately.
Explicit server query
Paste a signed raw transaction
Whitespace is removed in this browser before submission. The maximum decoded transaction size is 400,000 bytes.
Nothing has been submitted. The transaction stays in this browser until you press “Test acceptance”.
Point-in-time results
Mempool policy decisions
Purpose, privacy, and limits
Interpret a point-in-time answer
Node-specific policy
Andreas and Adam evaluate the same transaction against their own current mempool, chain state, fee floor, standardness rules, and package limits. Their answers can differ.
No broadcast
The backend uses Bitcoin Core’s read-only mempool acceptance check. It never calls a submission RPC and does not relay the transaction to Bitcoin peers.
Not a future guarantee
Conflicts, spent inputs, fee thresholds, ancestors, reorgs, or policy can change after the check. Acceptance also does not promise confirmation.
Usage limits
Up to 6 submissions per minute per IP address, with a maximum of 3 immediate requests. Testing both nodes still counts as one submission. Raw transactions may be up to 400 kB. Shared capacity is limited, so the service may temporarily return a rate-limit response when busy.
Privacy disclosure
When you submit, your full signed transaction and IP address reach BitcoinStats over the clearnet. The raw transaction is used in memory for this single check on the selected BitcoinStats-operated node or nodes and is not stored. Live metrics use only a first-party BitcoinStats endpoint; your browser contacts no third-party data provider.