pull down to refresh

that depends on how the batching is done. It's possible for multiple people to prepare several transactions off-chain and perform transaction cut through in such a way that only one utxo is consumed on the base layer. That is a form of batching, and lightning channel closures are an example: all the transactions that happened in the channel get "cut through." Only a single utxo is consumed on the base layer, and two new utxos are usually created from it. But that single transaction "includes" a whole batch of transactions that happened inside the channel. I want more stuff like that.
We all want more stuff like that. But you don't know what is happening off-chain from looking at the chain - it doesn't factor into the number of on-chain transactions in blocks. Some blocks are filled with a single inscription jpeg "transaction".
reply
But you don't know what is happening off-chain from looking at the chain
I can see that the transactions that are in there don't look optimized. I can make tools to further optimize them, encourage their use, and make websites that help track this stuff so that progress is more measurable.
Some blocks are filled with a single inscription jpeg "transaction"
I want less of that
reply