I think the spec is supposed to be one ball per second, but I guess that's not really adhered to.
Tangentially, I think it'd be interesting to use something like this to explain the networking concepts of throughout, latency, jitter, baud vs bits per second, symbol rate and bits per symbol.
You can find analogous examples in the main video to compare to all of those concepts.
Nothing in IPv6 says you have to stop dividing at the /64 level.
There has been some hardware that takes a bit of a performance hit when doing route lookups that are longer than /64 in the past, but if you're doing this all in software on an end host, that's not an issue.
Go ahead and divide up that /64 to smaller blocks for your classification purposes, you'll still have plenty.
Tangentially, I think it'd be interesting to use something like this to explain the networking concepts of throughout, latency, jitter, baud vs bits per second, symbol rate and bits per symbol.
You can find analogous examples in the main video to compare to all of those concepts.