On the old website, we had three graphs one under the other displaying all the important mempool information. That has now changed to one graph. If you want to see different parameters, you have to select one of the other tabs.
Yeah, I think it's a good change though, especially the fact that the "weight" graph is the default one. The majority of people who use Jochen's site are using it to help them estimate an appropriate fee to choose. In such a case the "Mempool Weight in vMB" is the only graph that really matters. It is more or less irrelevant to the majority of users how many transactions there are at each fee band or the cumulative total of fees waiting to be claimed by miners. Also good that he has made it explicit that the graph is in vMB as there has been some confusion about this before. 
Topic: [help]Payment is not confirmed for a long time (Read 133 times)
It actually always showed the mempool in terms of vMB. Although it called it MB in the graph titles, the text at the bottom explained it was using virtual bytes.
Yeah, I knew that. But the interface is now different. On the old website, we had three graphs one under the other displaying all the important mempool information. That has now changed to one graph. If you want to see different parameters, you have to select one of the other tabs. If your transaction hasn't already been confirmed, I think that it's a matter of minutes now.
OP's transaction confirmed around 8 hours ago. Going by the timestamps, it actually confirmed 10 minutes before OP made this thread. For future reference OP, obfuscating the addresses like you have done does nothing to protect your privacy. Simply by knowing the input and output amounts, I was able to locate your transaction in under 10 seconds.It now shows transaction weight in vMB by default
It actually always showed the mempool in terms of vMB. Although it called it MB in the graph titles, the text at the bottom explained it was using virtual bytes:Quote
Note that sizes include the segwit discount, i.e., the graphs show virtual byte (weight divided by four). For segwit transactions, the real size of the transaction is a bit larger than the virtual size. So for the BTC and LTC chains, a block will always take at most 1 MB from the mempool, even if it is bigger than 1 MB, because the lower diagram already shows the size in vbyte (with the segwit discount included).
I paid the merchant’s bitcoin address equal to $27 in bitcoins, but it was not confirmed after waiting for a long time. What is the reason? Is it a matter of handling fees?
From screenshot you posted it looks like you paid lower fee and you used legacy address so you have the option to wait for confirmation, and I think it should happen this weekend on saturday or sunday.
Second option you have is to pay higher fee if you used RBF replace-by-fee flag in your transaction and in future always check Bitcoin mempool.space before you send any transaction.
Mempool looks good and I think your transaction should be confirmed now.
currently waits to get 1 confirmation. 10 sats/vbyte should be enough for the weekend.
Ever since bitcoin price stabilized in the $55k range with smaller fluctuations the transaction fees have been coming down and currently a transaction with only 6 satoshi/vbytes can be confirmed in the next block. You can always check out the mempool status from this site: https://jochen-hoenicke.de/queue/#BTC,24h,weight
The bitcoin mempool is already down and confirming transactions in the 7-10 sat/vMB region. If your transaction hasn't already been confirmed, I think that it's a matter of minutes now.
Btw, has anyone noticed that Johoe's Bitcoin Mempool site has been redesigned? It now shows transaction weight in vMB by default, and you can change it to display the pending transaction fees in BTC or the unconfirmed transaction count from the three buttons on the top right.
Btw, has anyone noticed that Johoe's Bitcoin Mempool site has been redesigned? It now shows transaction weight in vMB by default, and you can change it to display the pending transaction fees in BTC or the unconfirmed transaction count from the three buttons on the top right.
Does this merchant support RBF transactions? If not, they might not recognize your tx if you decide to bump the fees, so yeah waiting might be the best option. Especially if they already confirm your tx is pending and currently waits to get 1 confirmation. 10 sats/vbyte should be enough for the weekend.
Yes it needs a higher fee. Can you wait for it to confirm on its own, it might be worth waiting if it's only 4mb away from the tip (normally a few hours).
If not you can right click the transaction and click to bump the fee and make it enough to confirm within the next block when the dialog box opens.
If not you can right click the transaction and click to bump the fee and make it enough to confirm within the next block when the dialog box opens.
Hello all,
I paid the merchant’s bitcoin address equal to $27 in bitcoins, but it was not confirmed after waiting for a long time. What is the reason? Is it a matter of handling fees?
Please check the link for the screenshot of the transaction: https://drive.google.com/file/d/1fqH8_AnDTm1DpKfN1ZNJtxDshXINhhma/view?usp=sharing
Thanks
I paid the merchant’s bitcoin address equal to $27 in bitcoins, but it was not confirmed after waiting for a long time. What is the reason? Is it a matter of handling fees?
Please check the link for the screenshot of the transaction: https://drive.google.com/file/d/1fqH8_AnDTm1DpKfN1ZNJtxDshXINhhma/view?usp=sharing
Thanks
Jump to: