Replaces #10225 as it caused intermittent failures for some users.
Difference: gave up on making a “fast running” test and upped the blockchain size and spam count to avoid the scan finishing before the abort call. Moved test down to extended tests.
Test runs in roughly 2 minutes on my local machine. The blockchain generation part takes roughly 1m20s. @jnewbery Does this work on your end?