I've created an initial implementation for concurrent evaluation of confirmability. In libbitcoin validation and confirmability are distinct checks as they have distinct ordering constraints. Download is unordered by block, validation is partially ordered by block whereas confirmability is totally ordered by block. Yet, as with validation, confirmation is unordered by tx, and fuller blocks have around 4 thousand txs. This provides an opportunity to concurrently determine confirmability within a block, similarly to how we do with validation, which is concurrent by tx across multiple blocks.