dTAOscan block 8,584,959 · 5m ago Bittensor dTAO subnet explorer · read straight from chain
Chutes0.072152τTargon0.053733τlium.io0.053291τVanta0.030004τAffine0.056381τdeprecated0.02295τScore0.037812τiota0.033093τGradients0.017954τNOVA0.022147τHone0.014635τBitMind0.012285τblockmachine0.010681τHippius0.016879τRidges0.011962τActual0.048805τCacheon0.010599τ404—GEN0.010166τApex0.008541τData Universe0.006874τengy0.012452τdeprecated0.008501τTrajectoryRL0.008475τDojo0.006728τdeprecated0.006976τBitcast0.010658τgm0.013213τSwap0.006509τReadyAI0.006251τEnigma0.008712τChutes0.072152τTargon0.053733τlium.io0.053291τVanta0.030004τAffine0.056381τdeprecated0.02295τScore0.037812τiota0.033093τGradients0.017954τNOVA0.022147τHone0.014635τBitMind0.012285τblockmachine0.010681τHippius0.016879τRidges0.011962τActual0.048805τCacheon0.010599τ404—GEN0.010166τApex0.008541τData Universe0.006874τengy0.012452τdeprecated0.008501τTrajectoryRL0.008475τDojo0.006728τdeprecated0.006976τBitcast0.010658τgm0.013213τSwap0.006509τReadyAI0.006251τEnigma0.008712τ

Cross-subnet synergy

the validators that hold the network together

Subnets are not islands. The clearest connective tissue is the validator set: a small group of validators scores miners on many subnets at once, so their behavior, and their failures, propagate across the network. This is that overlap, computed from the on-chain validator permits, one validator per row with every subnet it secures. New to this?

validators spanning 2+ subnets
25
the cross-subnet operator set
most connected validator
112
5E2LP6...eZ5u secures 112 subnets
shared owner keys
0
every subnet uses a distinct owner coldkey; entity links are off-chain, not on it
coverage
128/128
subnets with validator data indexed so far

Validators by cross-subnet reach

Reach = how many subnets one validator secures at once. A high number is a single point of correlation across the network. Click any validator to drill into its per-subnet scores.

#1 5E2LP6...eZ5u → 112 subnets
#2 5G9hfk...wrc5 → 77 subnets
#3 5FLoWC...Rv8m → 70 subnets
#4 5CsvRJ...2zVp → 67 subnets
#5 5GP7c3...VCMi → 38 subnets
#6 5HbScN...FZdT → 38 subnets
#7 5EtUYR...tvzs → 17 subnets
#8 5HmkM6...25H7 → 15 subnets
#9 5FeKsR...9DGg → 13 subnets
#10 5G1NjW...nChe → 11 subnets
#11 5HK5tp...EpeN → 11 subnets
#12 5DqctM...UiQB → 8 subnets
#13 5DvDyp...diFp → 7 subnets
#14 5Cw4E2...u5cs → 4 subnets
#15 5HptFX...hzeT → 3 subnets
#16 5EFcCV...b1b9 → 2 subnets
#17 5FeNwZ...UZmo → 2 subnets
#18 5ELREh...qwVh → 2 subnets
#19 5CqRMu...b9Ed → 2 subnets
#20 5Fy3Mj...hQCY → 2 subnets
#21 5Ggasr...xGTV → 2 subnets
#22 5EZ52J...7kR8 → 2 subnets
#23 5Eo3Ha...8MWD → 2 subnets
#24 5DyQkk...3XUk → 2 subnets
#25 5CaJha...ZC24 → 2 subnets

Method: for every subnet we index the per-UID validator permit straight from Subtensor, then group by validator hotkey. A validator on many subnets is a single point of correlation (and of failure) that a per-subnet view hides. Next: capital rotation between pools, and entity linkage (github org, website, funding) for the operator graph that ownership keys deliberately do not reveal.