How does Kaspa balance parallel blocks with consensus complexity?

When building its virtual state, Kaspa picks virtual parents from candidate blocks while enforcing a cap on how large the resulting mergeset can grow. Virtual parents are the reference points the protocol selects to represent the current tip of the blockDAG; the mergeset is the collection of blocks being folded into consensus in that step. By capping the mergeset size, the system can include many parallel blocks — supporting Kaspa's ability to accept blocks created at the same time — without letting the computational work of reaching agreement spiral out of control. For a beginner, this means Kaspa's parallel block acceptance isn't unlimited: there is a deliberate ceiling that keeps the network fast and practical even at high block rates.