Next scheduled rescrape ... in 3 days
Version 1
Last scraped
Scraped on 15/09/2025, 09:26:19 UTC
Hello,

I've recently got a new laptop (for my daily stuff) and I've downloaded Bitcoin Core and I run it as a pruned node.
I have signed a transaction with my offline Bitcoin Core node.
Then I transferred the PSBT to my online pruned Bitcoin Core node.
The transaction, though it was signed with a high fee (~3.5 sats/vB), it stayed in the memory pool for more than 30 minutes.

Can anybody explain to me why? I am happy that things like this happen, because I get the chance to familiarize more with Core.

Here is a screenshot (when it was still waiting in the mempool):



Hint:
It looks like my node updates its status quite late. Now, it says that my transaction is 1/unconfirmed when in reality it's confirmed!
Original archived Transaction stayed in the Memory Pool for too long
Scraped on 15/09/2025, 09:20:46 UTC
Hello,

I've recently got a new laptop (for my daily stuff) and I've downloaded Bitcoin Core and I run it as a pruned node.
I have signed a transaction with my offline Bitcoin Core node.
Then I transferred the PSBT to my online pruned Bitcoin Core node.
The transaction, though it was signed with a high fee (~3.5 sats/vB), it stayed in the memory pool for more than 30 minutes.

Can anybody explain to me why? I am happy that things like this happen, because I get the chance to familiarize more with Core.

Here is a screenshot (when it was still waiting in the mempool):