← all tokens
2UtrhwVheyP5CNAZfBcZVFajjpMU8fqD2qPsRyuHpump
The mintslot 451,434,211
token programTokenzQdBNbLqP5VEhdkAS6EPFLC1PHnBqCXEpPxuEb
supply999999999999908
decimals6
mint authoritynull: revoked
freeze authoritynull: revoked
Fee configurationslot 451,434,211
unreadPENDING
the balance could not be read. This is not a zero
Held by the configuration account. It is addressed to nobody and nobody has taken it, so it is not claimable and certainly not received.
config account8vY65pdCUQLf5oXHqYVYA5Qyg2QWzKUYMNisA1UbV22k
adminEbMBZi73ic7Vs2MBukwW5NTGPoHbzu9qsApmAR3h4W22
byte 751: shown, not interpreted
shareholders1
holder 08vY6…V22k · 100.00% (10000 bps)
shares add up to10000 bps: the whole fee
These were printed as raw bytes until 2026-09-22, with a note saying the share reading was wrong: they read 10000 in 3,874 of 3,880 single-holder configs, yet 0 of 120 multi-holder configs summed to 10000. The control was right to stop the claim and wrong about why. The field was always basis points. The stride was wrong. An entry is 34 bytes, not 40, so every holder after the first was being read six bytes inside the previous one’s share. Re-read at 34, 24 of 24 multi-holder configs sum to exactly 10000.