Bitcoin source
Nick
Bitcoin Core v29.4.0 · the node whose new mempool transactions trigger this relay.
- Tip
- 972,070Synced
- Peers
- IPv4 34 IPv6 15 49 peers total (39 in / 10 out)
- Mempool
- 131 MB
- Min fee
- 0.10 ṩ/vB
BTC → BLAKE Relayability Test
You can use this tool to check a signed Bitcoin transaction against the exact Bitcoin source and BLAKE target nodes used by my BTC → BLAKE Relay. The original bytes are tested independently by Nick (a node running Bitcoin Core v29.4.0, following the Bitcoin chain and observing newly accepted mempool transactions) and Luke (a BLAKE-enabled node running Bitcoin Knots v29.4.2.knots20260508).
The check is explicit and read-only: it does not broadcast, relay, queue, or store the transaction. A positive result describes this moment only, not guaranteed later relay or confirmation.
BLAKE target
Luke
BLAKE-enabled Bitcoin Knots · the node that independently applies BLAKE chain state and mempool policy.
- Tip
- 977,923Synced
- Peers
- IPv4 5 IPv6 1 Onion 4 10 peers total (0 in / 10 out) · routed through Tor
- Mempool
- 32.3 MB
- Min fee
- 0.10 ṩ/vB
Paste a signed raw transaction
Whitespace is removed in this browser. Only serialized transaction hex is accepted; never paste a seed, private key, descriptor, or PSBT.
Nothing has been submitted. The transaction stays in this browser until you press “Check relayability”.
Point-in-time result
Relay path decision
Interpret the result carefully
“Relayable now” is not a promise
Chain state, conflicts, fee floors, relay mode, and queue pressure can change before Nick sees the transaction.
Parents matter
A missing-inputs result may be temporary when an unconfirmed parent has not yet reached a node. This single-transaction check does not submit a package.
No broadcast
The backend invokes only transaction decoding and read-only mempool acceptance checks. It never calls a submission RPC.
Privacy disclosure
When you submit, the full signed transaction and your IP address reach this site over the clearnet. The transaction is forwarded over a pinned, encrypted connection to my Stella server in Vienna, held in memory only for this check, and independently evaluated by Nick and Luke using the read-only testmempoolaccept RPC. It is never broadcast, relayed, queued, or stored. For highly sensitive transactions, run testmempoolaccept on your own nodes instead.
Usage limits
Up to 6 submissions per minute per IP address, with a maximum of 3 immediate requests. Raw transactions may be up to 400 kB. Shared capacity is intentionally small.