how many transactions a block can hold(max)?

[Gol]

Hello all,
how many transactions a block can hold(max)?

Cheers!
Gol.

[maaku]

The limitation is on block size, not the number of transactions. A block cannot exceed 1MB in size, in the serialization format used by the p2p message protocol. The size of a transaction can vary.

[Gol]

Thanks!

so when hashing a block and the block become full all waiting transactions are...where? 


Gol.

[maaku]

In a data structure in memory (the mempool), where they are kept for the next block.

[Gol]

thank you!

[Peter Todd]

You might find this interesting: https://en.bitcoin.it/wiki/Maximum_transaction_rate

Though remember that you can make even shorter insecure transactions by using empty scriptSig/scriptPubKeys.

[Hyena]

Bitcoin-QT doesn't ask me to add tx fee for some transactions. However, it's been 6 8 hours and I'm still having 0 confirmations. Why is this? Is Bitcoin network overloaded?

[Automatic]

Bitcoin-QT doesn't ask me to add tx fee for some transactions. However, it's been 6 8 hours and I'm still having 0 confirmations. Why is this? Is Bitcoin network overloaded?

You may want to post your transaction hash.

[jdbtracker]

I think that it would be at about 5,000 transactions per block maximum, if all transactions stayed at only 200 bytes, we can go smaller but it'll take compression.

[Hyena]

Bitcoin-QT doesn't ask me to add tx fee for some transactions. However, it's been 6 8 hours and I'm still having 0 confirmations. Why is this? Is Bitcoin network overloaded?

You may want to post your transaction hash.

So I woke up this morning and see that the TX is now finally confirmed. Knowing that such things can happen and leave you in a disturbing void for some time I'd feel a need for some service that would allow me see if some pool has my TX queued and what could be the possible cause for delay. My initial thought was that because the TX didn't require a fee no miner wanted to confirm it and all the blocks got full. Other thought was that maybe someone was somehow disrupting the network on purpose.

[solex]

I think that it would be at about 5,000 transactions per block maximum, if all transactions stayed at only 200 bytes, we can go smaller but it'll take compression.

2,400 is a good working number to use for transactions (as measured by blockchain.info) in a max block
Recent example of 1,280 transactions using 687KB:

https://blockchain.info/block-index/465553/00000000000000014061615cf6f68bea2bc39c03d3d826c8fe9cf03469aeed10