Detailed stats are finally available!
Topic: BitcoinQueue.com ⏳ ★ Real-time Queue Charts 📈 - page 2. (Read 2387 times)
[MAJOR UPGRADE]
Detailed stats are finally available!
Detailed stats are finally available!
The current chart include zero-fees in "<10 s/B" area.
[LATEST NEWS]
Please note that data may be inaccurate as the engine was heavily improved over the last 24h, and needed several restarts.
From noon UTC today, transactions will stay in the queue for 3 days, i.e. 72 hours, mempool default.
All queue data has now been logged since around noon (UTC), i.e. 8 hours ago at time of writing.
Since about 30 minutes ago, a new version of the graphs is building, with fee groups of 10 satoshi increments, i.e.
Group 0: 0 (strictly zero fee)
Group 10: 0.xx -> 10
Group 20: 10.xx -> 20
Group 30: 20.xx -> 30
...
Group n: n.xx -> (n+10)
And the new area charts will show every group
Preview coming soon
[LATEST NEWS]
Please note that data may be inaccurate as the engine was heavily improved over the last 24h, and needed several restarts.
From noon UTC today, transactions will stay in the queue for 3 days, i.e. 72 hours, mempool default.
All queue data has now been logged since around noon (UTC), i.e. 8 hours ago at time of writing.
Since about 30 minutes ago, a new version of the graphs is building, with fee groups of 10 satoshi increments, i.e.
Group 0: 0 (strictly zero fee)
Group 10: 0.xx -> 10
Group 20: 10.xx -> 20
Group 30: 20.xx -> 30
...
Group n: n.xx -> (n+10)
And the new area charts will show every group
Preview coming soon
Matt,
Your chart has "fees <10 sat/byte". Does that include 0 sat/byte, or is it 1 - 9?
Your chart in no way resembles 21fees figure in this <10 category. What am I missing?
(infact, none of it tally's with bitcoin21fees.co? what am i missing
)
Your chart has "fees <10 sat/byte". Does that include 0 sat/byte, or is it 1 - 9?
Your chart in no way resembles 21fees figure in this <10 category. What am I missing?
(infact, none of it tally's with bitcoin21fees.co? what am i missing
)
[UPDATE] The engine has been completely rewritten to fit the ever-growing queue!
Transactions will be kept for 72h from now on, matching the default mempool retention of Bitcoin Core.
Sorry about the disruption in the charts, the queue had to be rebuilt from scratch. Another good news is that every transaction is stored separately into the database from now on, allowing for retroactive statistics to be (re)built in the future.
Transactions will be kept for 72h from now on, matching the default mempool retention of Bitcoin Core.
Sorry about the disruption in the charts, the queue had to be rebuilt from scratch. Another good news is that every transaction is stored separately into the database from now on, allowing for retroactive statistics to be (re)built in the future.
Very good job, OP, and good to have this in place ahead of the turmoil that will follow halving.
[UPDATE] The new transaction timeout has been set to 24 hours (instead of 8 hours previously)
Thank you all 
In the next few days, I will be adding breakdown tables and total tx fees per fee class in the data very soon, as well as more information about the average/median tx inclusion time in a block. I need to upgrade my backend first though.
In the next few days, I will be adding breakdown tables and total tx fees per fee class in the data very soon, as well as more information about the average/median tx inclusion time in a block. I need to upgrade my backend first though.
Interesting website, I was looking for something keeping track of such stats over time but couldn't find anything. Good job OP.
Good job 
Matt, I tried this before, but, I'll try again.
It looks to me that your chart does not include 50 sat/byte in the >= 50 sat/byte group. I think it is 51 sat/byte and over.
(comparing to bitcoinfees21)
Could you double check for me?
Thanks
ps. don't think the bug is fixed!
It looks to me that your chart does not include 50 sat/byte in the >= 50 sat/byte group. I think it is 51 sat/byte and over.
(comparing to bitcoinfees21)
Could you double check for me?
Thanks
ps. don't think the bug is fixed!
I have checked bitcoinfees.21.co and upon first look, the >=50 s/B group should (now) be correct on the charts, i.e. the teal colored area in the chart, currently about 8k out of about 20k in the queue.
Please also note that I had to transition data stream from an older version to a newer version of the process, so data should be more accurate starting about 16:00 UTC (4pm) today Jun 15.
BUT at any rate I will be working hard over the next few days to improve accuracy and debug the code
Sometimes it hard to keep up with the flow without switching to more expensive, multi-core server instances.
Thanks for your feedback, I will post updates here
UPDATE
There was a bug in the presentation of the stacked charts, where the cumulative values were used for each series instead of the correct data.
The bug has been fixed and all graphs are now correct.
Yes, but there is a much better transaction fee breakdown view coming up
There was a bug in the presentation of the stacked charts, where the cumulative values were used for each series instead of the correct data.
The bug has been fixed and all graphs are now correct.
Unfortunately, matts chart here is too vague to be able to judge how much fee to pay.
Yes, but there is a much better transaction fee breakdown view coming up
Excellent news. Keep up the good work!
Matt, I tried this before, but, I'll try again.
It looks to me that your chart does not include 50 sat/byte in the >= 50 sat/byte group. I think it is 51 sat/byte and over.
(comparing to bitcoinfees21)
Could you double check for me?
Thanks
ps. don't think the bug is fixed!
UPDATE
There was a bug in the presentation of the stacked charts, where the cumulative values were used for each series instead of the correct data.
The bug has been fixed and all graphs are now correct.
Yes, but there is a much better transaction fee breakdown view coming up
There was a bug in the presentation of the stacked charts, where the cumulative values were used for each series instead of the correct data.
The bug has been fixed and all graphs are now correct.
Unfortunately, matts chart here is too vague to be able to judge how much fee to pay.
Yes, but there is a much better transaction fee breakdown view coming up
Can you explain me if there was paid enough transaction fee for this transaction: https://blockchain.info/nl/tx/d62b6b403364bdf87faaa8a436baac510a35c6eed74fdfa1f891a083e5356348
Takes ages before this transaction processing still 0 confirmations.
Your transaction has enough fees: 4460 satoshi / 223 bytes = 20 satoshi / byte, but the queue is overloaded as you can see on the siteTakes ages before this transaction processing still 0 confirmations.
How much is "enough" fees?
20 sat/byte is not the "recommended" fee, for swift transaction.
Simply put, all other transactions in the mempool with higher fees than 20 sat/byte will be included in a block first.
https://bitcoinfees.21.co/ are currently recommending a fee of 60 sat/byte.
Yesterday it went up to 80 sat/byte.
Yesterday, even transactions paying say 50 sat/byte were "delayed".
If you want to get into the next block, you must include a fee equal to, or more than the top 2000ish fees in the mempool.
The problem* yesterday was that people paying the recommended fee of 50 sat/byte were outbid by people paying the latest updated recommended fee of 60 sat/byte.
People paying 60 were then outbid by people paying 70, then 80.
So even though people paid "recommended" fees (of 150% more than you), those "recommended" fees were then superseded.
Unfortunately, matts chart here is too vague to be able to judge how much fee to pay.
(recommended fee on https://bitcoinfees.21.co/ is now 90 sat/byte, 450% higher than your "enough" fee)
Nice website did not know before how to calculate the fees for each transaction. Normally I use XAPO and there you don't need to fill in any transaction amount. Will save this website could be really handy in the future.
Thanks, it's an early beta version and I'm working on a more real-time, better interface in the future. I also want to increase the expiry time from 8 hours to 72 hours to match the default mempoolexpiry.
Can you explain me if there was paid enough transaction fee for this transaction: https://blockchain.info/nl/tx/d62b6b403364bdf87faaa8a436baac510a35c6eed74fdfa1f891a083e5356348
Takes ages before this transaction processing still 0 confirmations.
Takes ages before this transaction processing still 0 confirmations.
Your transaction has enough fees: 4460 satoshi / 223 bytes = 20 satoshi / byte, but the queue is overloaded as you can see on the site
Nice website did not know before how to calculate the fees for each transaction. Normally I use XAPO and there you don't need to fill in any transaction amount. Will save this website could be really handy in the future.
Can you explain me if there was paid enough transaction fee for this transaction: https://blockchain.info/nl/tx/d62b6b403364bdf87faaa8a436baac510a35c6eed74fdfa1f891a083e5356348
Takes ages before this transaction processing still 0 confirmations.
Can you explain me if there was paid enough transaction fee for this transaction: https://blockchain.info/nl/tx/d62b6b403364bdf87faaa8a436baac510a35c6eed74fdfa1f891a083e5356348
Takes ages before this transaction processing still 0 confirmations.
Matt,
The 50 sat/byte is mixed with the "over 10 sat/byte"?
That makes 50 sat/byte look a bit spammy.
And it means it does not show what I am talking to Lauda about.
Would it be better 50 sat/bite and over (not 51 as now?)
10 - 49 sat/byte
The 50 sat/byte is mixed with the "over 10 sat/byte"?
That makes 50 sat/byte look a bit spammy.
And it means it does not show what I am talking to Lauda about.
Would it be better 50 sat/bite and over (not 51 as now?)
10 - 49 sat/byte
It's a stacked chart, meaning you can either read partitions or total.
I have arbitrarily chosen to make fee groups like this:
(1) 50 satoshi / byte or greater,
(2) 10 satoshi / byte or greater,
(3) all transactions
Obviously (2) contains (1), and (3) contains both (1) and (2). But you can easily use the difference to figure out the number of transactions / queue size with less than 10 satoshi / byte, over 50 satoshi / byte, between 10 and 50, etc.
"50 satoshi / byte or greater,"
or
"over 50 satoshi / byte"
Big difference.
(take this to your thread if you like)
It means exactly this:
Class 1: any transaction in the pool
Class 2: tx with fee >= 10 satoshi / byte
Class 3: tx with fee >= 50 satoshi / byte
(Class 1 - Class 2) = tx with fee less than 10 satoshi / byte
(Class 2 - Class 3) = tx with between 10 and 50 satoshi / byte
Currently there is an explosion both in size and number of transactions in the queue.
(reserved)
BitcoinQueue.com - Real-time Transaction Queue Statistics
BitcoinQueue.com is a simple stacked chart visualization of the transaction queue waiting to be included in the next block(s) of the blockchain.
It's pretty straightforward and it shows interesting data that I was willing to share :-)
https://www.bitcoinqueue.com
Twitter: https://twitter.com/bitcoinqueue
Facebook: https://www.facebook.com/bitcoinqueue
Reddit: https://www.reddit.com/r/Bitcoin/comments/4o2udc/bitcoinqueuecom_real_time_bitcoin_blockchain/
If you find it interesting, make sure to leave feedback here.
Jump to: