Transaction stayed in the Memory Pool for too long

[apogio]

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!

[LoyceV]

It looks like my node updates its status quite late.

Is your Current block height (CTRL-I to see it) lagging by any chance?

[apogio]

Is your Current block height (CTRL-I to see it) lagging by any chance?

Hi Loyce, no I've checked that. Is it perhaps because of my VPN? I checked with my VPN turned off, and it has the same issue, that's why I'm kinda confuzed. Not a huge deal,

[LoyceV]

I don't think a VPN matters. If your node is up to date, it should know which address is confirmed.

[BitMaxz]

This is pretty normal. I think it's not caused by the VPN since it's set to prune; it discards the old block first before downloading the latest block, validating, and rescanning.
Or maybe the peers you are currently connecting to are currently not providing the latest data, which is causing the delay.

I'd like you to try increasing the dbcache and maxconnections.
It might help speed things up, and having more peers might help receive the latest data faster than using the default.

[Mia Chloe]

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!

I believe it's all about how fast your node catches up with the rest of the network. The confirmation of your transaction actually depends on if it has been included in a block and not just it sitting in the mempool. Remember that your node actually has to download and fully validate that new block containing your transaction before it can officially update its status to confirmed. So there's  actually a very high chance that what what you're seeing is a temporary lag in synchronization.

Your pruned node should  be working  fine since it could correctly identify the transaction in the mempool but is waiting to process the block itself to reflect that it. is now confirmed. Check your network speed because sometimes it can contribute to this lag too.

[apogio]

I guess my observation was just an isolated event. I tried 3 more transactions in the exact same way and it worked flawlessly!

I should lock the thread now!

Thanks for the responses!