Andreas · Node #1
Nuremberg, Germany
Tools · Server query
Transaction Lookup
Look up a Bitcoin transaction by txid across four Bitcoin nodes I operate. The service checks Andreas → Adam → Martti → Hal and stops immediately when one node finds it.
The first two nodes cover their current mempools; the full archive nodes then provide historical lookup through their transaction indexes. This is a read-only lookup and never broadcasts anything.
Explicit server query
The query runs only when you submit a txid.
Submitted input: The public transaction ID is sent only after you explicitly submit it. Network effect: BitcoinStats checks Andreas, Adam, Martti, and Hal in that order and stops after the first match. The txid is not broadcast, stored in the URL or browser storage, or sent to a third-party provider.
Transaction IDBitcoinStatsSelf-hosted nodes in orderFirst match
No automatic requests, polling, retries, or third-party data providers are used after the page loads. The txid is not stored in the URL or browser storage.
Lookup path
Fast mempool checks, then full history
Adam · Node #4
Falkenstein, Germany
Martti · Node #3
Sankt Leon-Rot, Germany
Hal · Node #2
Sankt Leon-Rot, Germany
A successful match ends the sequence, so later nodes receive no request. 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
Purpose, privacy, and limits
What the result means
Found in a mempool
The transaction is currently known to the first matching 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. Shared capacity is limited, so the service may temporarily return a rate-limit response when busy.
Privacy disclosure
When you submit, your IP address and the public txid reach BitcoinStats over the clearnet. The txid is used for this one first-party lookup, is not placed in the URL or browser storage, and is not written to the endpoint access log. Your browser contacts no third-party explorer or data provider.