I have a bitcoin transaction thatβs showing on my node mempool but not on any other block explorersπ€¨any idea how to fix? #asknostr
Discussion
Whatβs the txn id?
16b7c8ba8a4f5fae315834197b3480e4cfa86b4b8c995abaa068500bf758b387
Not found, sure you copied it correctly?
Yessir, thatβs what itβs doing for me as well, I can see it on my node but not on public mempools. Very weird, the transaction is linked to a lightning channel anchor but it should be unlocked, I bumped the fee but the original transaction also isnβt showing. The ID for that one is
6b9b79c5d11046c42569b60d98cb71a121e48ca7e1e4e7658cc1d540d3effd19 
I see it, 1 confirmation.
Your node probably didn't get the transaction out to any other nodes. I had it happen once because of a network issue. You can get the data out of your node and rebroadcast the transaction.
Does your node have many connections? You could attempt to broadcast via Coinb.in
Each node maintains its own mempool. The mempool is a collection of unconfirmed transactions stored in a Bitcoin node's memory, waiting to be included in a block. However, the mempool is not uniform across all nodes due to the following reasons:
1. **Transaction Propagation Time**: It takes time for a new transaction to propagate across the network. Different nodes may hear about transactions at slightly different times.
2. **Node Policies**: Not all nodes have the same transaction acceptance policies. Some nodes might refuse to accept a transaction if its fee is too low, or for other policy reasons.
3. **Mempool Size and Limits**: Nodes might have different hardware capacities. Some nodes set limits on the maximum size or number of transactions in their mempool to prevent running out of memory. If the mempool reaches its limit, the node might start dropping low-fee transactions.
4. **Node Restart and Uptime**: If a node goes offline or is restarted, its mempool might be cleared, and it would then start building it up again based on new transactions and what it hears from peers.
5. **Mempool Eviction**: If a transaction remains unconfirmed for a long time (perhaps due to a low fee), some nodes might eventually drop it from their mempool.
Due to these factors, while there's a significant overlap, the exact contents of the mempool can vary from one node to another.
RBF or wait it out π€·ββοΈ
Okay so itβs now confirmed 3 hours later but it never showed up as pendingπ€£π€£weird one today but thanks for all ur replies!!
This is an interesting thread, maybe it points to the importance of running your own node! Is it possible this transaction would not have broadcasted properly if his node wasn't keeping it in his mempool?
Thatβs a thought that didnβt come to mind, if that actually is the case then Iβm very happy I recently started this nodeπ€£π€£π€£
