Andreas · Node #1
Nuremberg, Germany
Tools · Server query
Transaction Lookup
Look up a Bitcoin transaction by txid across five Bitcoin nodes I operate. With All nodes, the service queries Andreas, Adam, Peter, Martti, and Hal and reports every node’s result. You can also query one selected node only.
Andreas and Adam cover their current mempools. Peter checks its Libre Relay mempool. Martti and Hal check both their current mempools and the full historical chain through their transaction indexes. After a match, you can explicitly request the serialized transaction hex from the same self-hosted source and open it in the local-only Raw Transaction Decoder. This is read-only and never broadcasts anything.
Lookup path
Five independent node results
Adam · Node #4
Falkenstein, Germany
Peter · Node #6
Sankt Leon-Rot, Germany
Martti · Node #3
Sankt Leon-Rot, Germany
Hal · Node #2
Sankt Leon-Rot, Germany
With All nodes selected, every node receives the read-only lookup even after another node has found the transaction. See Node Details for hardware, operating systems, roles, connectivity, and current operational data.
Explicit server query
Enter a transaction ID
Paste a 64-character Bitcoin txid. Uppercase hexadecimal is accepted and normalized locally before submission.
Nothing has been submitted. The txid stays in this browser until you press “Look up transaction”.
Lookup result
Node search
Serialized transaction hex
Click “Load raw transaction” to retrieve the serialized transaction hex. This sends one additional request containing the txid.
Explicit server query
The query runs only when you submit a txid.
Submitted input: The public transaction ID, selected node scope, and requested lookup action are sent only after an explicit click. Raw transaction hex is never submitted by this tool. Network effect: With All nodes selected, BitcoinStats queries Andreas, Adam, Peter, Martti, and Hal and reports every node’s result; you may instead query one selected node. After a match, an explicit second action can retrieve raw hex from the same self-hosted source. No third-party provider is used. A deep URL can pre-fill the public txid and node but never runs a lookup automatically. The decoder handoff uses tab-scoped sessionStorage once and removes it immediately after reading.
Transaction IDBitcoinStatsSelected self-hosted nodesPer-node results
A deep lookup URL only pre-fills the form; it never queries a node until you press the button. There is no polling, retry loop, or third-party data provider. Opening raw hex in the decoder uses a one-time
sessionStorage handoff that the decoder immediately removes.Purpose, privacy, and limits
What the result means
Found in a mempool
The transaction is currently known to that node’s mempool. It can still be replaced, evicted, conflicted, mined, or removed after the lookup.
Found in a block
A full archive node located the transaction through its transaction index. The result includes its block, height, time, and current confirmation count.
Not found is scoped
“Not found” means only that none of the queried nodes found the txid at that moment. It is not proof that the transaction never existed, especially if coverage was partial.
Genesis exception
The Genesis coinbase is recognized locally, so no node is queried. Bitcoin Core deliberately excludes it from ordinary transaction lookup, and its 50 BTC output was never added to the UTXO set, so it cannot be spent. See the relevant RPC handling and chain parameter note.
Usage limits
Up to 6 submissions per minute per IP address, with a maximum of 3 immediate requests. A separate raw-hex request counts as another submission. Shared capacity is limited, so the service may temporarily return a rate-limit response when busy.
Privacy disclosure
When you submit either lookup, your IP address and the public txid reach BitcoinStats over the clearnet. Only my nodes are queried; no third-party API is used. Responses are marked no-store, request bodies and returned hex are not persisted by the service. “Open in Raw Transaction Decoder” uses a one-time sessionStorage handoff that the decoder removes as soon as it reads it. The shareable deep URL contains the public txid, but analytics normalizes it to the base tool path.