how many BTC-transactions are stored in 1 block (1MB)

[joe1234]

Hello forum

how many BTC-transactions are stored in 1 block (to my knowledge 1 block is 1MB)?

Thank your for your feedback!

Joe

[1714029278]

1714029278

[1714029278]

1714029278

[ranochigo]

Depends. Since the block limit is with the size, not the number of transactions, the number of transactions that can be in a block will vary according to the size of the transactions in the block. A transaction with one input and an output would be about 226 bytes. Using that as a gauge, a block can fit a maximum of 4424 transactions though that has never happened before.

The miner has the rights to include or exclude any transaction. Hence, the block might not even be filled and can just have one transaction which is the coinbase transaction.

[Thirdspace]

Height   Age   Transactions   Total Sent   Relayed By   Size (kB)   Weight (kWU)
497758   24 minutes   2616   5,199.04 BTC   BTC.TOP   1,089.12   3,992.59
497757   25 minutes   2556   9,520.10 BTC   BitClub Network   1,097.17   3,992.61
497756   30 minutes   2302   10,686.47 BTC   ViaBTC   1,103.23   3,993
497755   33 minutes   2428   22,867.79 BTC   SlushPool   1,077.72   3,992.85

a quick look on bc.info site should answer your question
1 MB could fit averagely 2500 transactions, which mean average 400-500 bytes per tx
if average fee is 100 sats/byte, then each block can give additional 1 BTC
I'm pretty sure it would reach even higher than that with recent high minimum miners fee

[nullius]

how many BTC-transactions are stored in 1 block (to my knowledge 1 block is 1MB)?

Blocks are not limited to 1MB:  The concept of a “block size” is obsolete.  With Segwit, there is no longer a block size limit at all; instead, there is a block weight limit of 4000000 bytes:

Code:

/** The maximum allowed weight for a block, see BIP 141 (network rule) */
static const unsigned int MAX_BLOCK_WEIGHT = 4000000;

Each transaction has its “weight” calculated, and the total is limited. This is specified by BIP 141:

Blocks are currently limited to 1,000,000 bytes (1MB) total size. We change this restriction as follows:

Block weight is defined as Base size * 3 + Total size. (rationale^[3])

Base size is the block size in bytes with the original transaction serialization without any witness-related data, as seen by a non-upgraded node.

Total size is the block size in bytes with transactions serialized as described in BIP144, including base data and witness data.

The new rule is block weight ≤ 4,000,000.

It sounds complicated; but this is actually designed to avoid making transaction selection more difficult for miners.  As in many engineering matters, the most obvious way would have negative side effects which can be ameliorated by careful design.

Edit:  Refer to the code!

[hopeAo]

Hello forum

how many BTC-transactions are stored in 1 block (to my knowledge 1 block is 1MB)?

Thank your for your feedback!

Joe

A block cannot exceed 1MB in size, in the serialization format used by the p2p message protocol. This limit is to prevent huge blocks that clog the network and may be removed if the number of transactions in the network ever grows such that the limitation is a serious factor.
The size of a transaction can vary, so miners can only include as many transactions that will fit into that 1mb space. 

You might get up to 4000 transations in a block.

[bob123]

~snip~
how many BTC-transactions are stored in 1 block (to my knowledge 1 block is 1MB)?
~snip~

~snip~
You might get up to 4000 transations in a block.

To get the real maximum amount of transactions being possibly in one block:
Consider a block filled with the smallest possible (segwit-)transactions (1 input / 1 output)
The real crucial point is the sum of the non-witness part.
With 82 byte (non-witness part) transactions and a non-witness blocksize of 1MB we get a maximum of 12.195 transactions / block.
Compared to the corresponding non-segwit transactions (with size of 192 byte) this would be a maximum of 5.208 transaction / block.
Please note: This is an extreme example, since TX's mostly aren't only made of 1 input / 1 output. But it shows the limit of transactions (currently) possible.