How many transaction lanes can a single Kaspa block contain?

Consensus rules allow each Kaspa block to draw transactions from at most 50 distinct non-coinbase lanes. A lane is a grouping category for transactions; capping the number of lanes per block limits how much local SMT (Sparse Merkle Tree) update work each node must perform when it processes that block. At Kaspa's default pace of 10 blocks per second, the 50-lane ceiling translates to a worst-case bound of 500 user-lane updates per second across the entire network. For developers or power users, this matters because transactions whose lane would push a block past the 50-lane limit are simply deferred to the next block rather than dropped.