← all tokens
Termux AI TMUX
Z3moLVEacRDPQLVQ9JTpEFXJ3rG4sHR1WEh5CS9pump
The mintslot 451,460,337
token programTokenzQdBNbLqP5VEhdkAS6EPFLC1PHnBqCXEpPxuEb
supply999581394834523
decimals6
mint authoritynull: revoked
freeze authoritynull: revoked
Fee configurationslot 451,460,337
0.0080 SOLPENDING
8,017,920 lamports · read at slot 451,460,337
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 accountGneqnhVDZNPbjkqmjPrN4E4bSpVb4VgcB642C2X9uZLU
admin4jj8XK6PQFQ2rzgDFhcKNeqnqAY5GpdR3WHHK3PxGYF4
byte 751: shown, not interpreted
shareholders2
holder 04jj8…GYF4 · 97.00% (9700 bps)
holder 19uzd…RHNA · 3.00% (300 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.