It does take some hours for some transactions when the mempool gets stuck at higher SATs/byte due to more clog and the sender sent the coins with ~0 - 0.5 SATs/byte during that time. I was watching some transactions yesterday where some 0 fee transactions were not going through for hours during the mempool clog when minimum fee to get in early changed to 5 SATs/byte. -snip-
I just like to mention that the current minimum fee that a node with default relay setting is 1sat/B; the chance that a <1sat/B fee tx will propagate is close to zero.
Those "
0.something/B" that you see on outdated/buggy blockexplorers like blockchain.com must have SegWit data in them that they fail to compute correctly
The addresses tab used to be visible by default and that led to people being confused about why they had so many addresses. They were under the mistaken impression that one wallet = one address. So they hid that tab by default and now you have people complaining about the receive tab handing out different addresses each time!
Isn't that "
fix" counter-intuitive?
Because it will eventually change after one transaction, then the newbie will think that his (
single) address changed.
I think it has something to do with discouragement of "
address reuse" which actually works for newbies.
@
davidshu1 It's impossible to
delete replace an address from the "
receive tab" without receiving funds to that particular address.
But this topic looks like already solvedand the main issue must have been: after panicking from the "
deleted address" (
'coz it was replaced) you restored using the seed (
post#5) then just waited for the client to sync to be able to display the transaction that actually went through in the first place.
We'll be glad if you can confirm this