When the Bitcoin network is overloaded, it means there are too many transactions, and the blockchain's throughput isn't enough for everyone. To get a transaction included in a block, you need to pay a higher fee. At the same time, all transactions sent to the network are visible as unconfirmed in explorers like mempool.space.
But with Solana, the sender of the transaction told me that the network is overloaded, so the transaction isn't going through. I asked for the transaction hash, but they told me that there isn’t and can’t be a hash because the transaction itself isn’t being created due to network overload.
Can anyone explain how this works? Is it true that network overload causes difficulties not with transactions being processed, but with their creation?
That's how I see it (from my knowledge, that is, I may be wrong on the matter):
On SOL, transaction processing differs from ETH or BTC.
They do not go into the queue of the mempool, instead, they are sent to the validators for execution.
Said validators stream "shards" to the network to process.
Because of that, network overload affects transaction creation and propagation.
Users may not see their transactions because RPC providers (which handle transac. submission) become overloaded, and can't send transactions to validators in time.
Even if they are created, they may not reach validators fast enough. So they expire before being processed.
So the blocks are not produced efficiently.
(source of info from which I grasped some of my understading: Solana Congestion: Explained )