it's confirmed now
there have been a lot of max sized blocks lately, probably the reason it took a while.
Your tx was at 1722pm utc, there was only one block that wasn't full between then and now, that being 343315. If you want faster confirmations, increase fee to 0.00011
(also it was 9xx bytes, so like at the very back of the queue)
there have been a lot of max sized blocks lately, probably the reason it took a while.
Your tx was at 1722pm utc, there was only one block that wasn't full between then and now, that being 343315. If you want faster confirmations, increase fee to 0.00011
(also it was 9xx bytes, so like at the very back of the queue)
ah i see, i didnt know there was a priority for data size as well, I assumed it was a simple FIFO queue for transactions with priority for fees, thanks for the info
The fees are correlated with the "size" of the Tx , if you put 0.0001 btc / 900 byte TX and someone send a Tx with (always) 0.0001 btc/ 300-400 byte ;
the second has a major probability to be included first in a block.
I told you just to be patient mate .