Faucet Troubleshooting
Use this guide to diagnose rejected addresses, pending requests, explorer lookup problems, and out-of-funds messages.
Lookup a Signet Transaction or Address
Paste a Signet transaction ID or address. This browser-side helper links to the public Signet explorer and, when possible, checks the mempool.space Signet API.
Address Rejected
Mainnet addresses, regtest SegWit addresses beginning with bcrt1, and malformed strings are rejected. Legacy regtest, testnet, and custom signets can share an accepted address encoding. Confirm your wallet uses default Signet: a checksum cannot establish its network.
Request Still Pending
Requests are batched before broadcast. A pending request usually means it is waiting for the next batch, the faucet node is catching up, or the mempool is temporarily not accepting the transaction. Check faucet status before submitting again.
Out of Funds or Rate Limited
The faucet can run out of spendable outputs during heavy use. When funds are unavailable, watch the public status page. Rate limits are separate: each IP address and receiving address can request at most five times in a rolling 24-hour window. New blocks and a higher faucet balance do not reset that quota.
Explorer Disagrees With Your Wallet
Hosted explorers can lag or disagree with your local node mempool. For serious testing, confirm against your own Signet node with bitcoin-cli -signet gettransaction, getrawtransaction, or wallet balance commands.