Second Block Algorithms
Every algorithm for all 65 Roux second-block cases, ranked by how often top solvers actually use them.
What makes this database different
Ranked by real solves
Ordered by what top solvers actually use, not by popularity votes.
Pro usage counts how many reconstructed Roux solves inserted a second-block pair with an algorithm, counting both the front and back slot. Alongside it sits each algorithm's community vote count from SpeedCubeDB, so you can see where the crowd and the pros disagree.
A grip bar asks a different question of the same solves: how many were done one-handed. One hand rewards regrip-light, rotationless algorithms, so a fat pink slice means the algorithm suits one hand better than the two-handed mainstream picks it. Its header switches the whole table between both grips, two-handed only and one-handed only.
- One-handed
- Two-handed baseline
One row per algorithm
The same algorithm written in different ways collapses into one row.
Alg lists repeat themselves: the same turns show up reordered, behind a different alignment, or just spelled a different way - a slice M written as r'R , a wide l written as x'R . Those all move the cube through exactly the same states, so we fold them into one row and add up their votes.
Mirrors are the exception: a left-handed version keeps its own row, because doing an algorithm on the other side is a genuinely different thing to learn.
Reductions
Algorithms that pass through an easier case show you where.
Plenty of these algorithms start by turning the case into an easier one and then solving that. Where they do, hovering the row (or tapping it, on a phone) marks the point its moves reach that case, so you can see the algorithm you already know inside the one you don't.
Everything after the marker is that easier case's own solution - so a case you find hard reads as a short setup into one you have already learned. On this set 13 of the listed algorithms reduce into Jb alone. The markers only appear on the row you are pointing at, so the table itself stays still as you read down it.
Grouped into triggers
Every algorithm is boxed into the triggers your hands already know.
Grouping gives an algorithm a shape you can picture instead of a string you have to spell, and it exposes the family resemblances: algorithms built from the same trigger carry the same colour, so the one you already know gives you a head start on the next. The Rightie RUR'U' gets one colour, the sledgehammer R'FRF' another. Hover any box for its name.
Cubers have always marked triggers by hand, in parentheses: F (R U R' U') (R U R' U') F'. The boxes are that convention drawn instead of typed, and they are worked out from the moves themselves rather than stored per algorithm - so every algorithm in the database has them, including the ones nobody ever bracketed.
Second Block Overview
most-used last-slot algorithms for every case