A program is only what it does. Watch it work.
Documentation describes a protocol. Axionex reads it the other way round — from the chain outward. Point it at a program ID and it pulls the transactions flowing through it right now, then maps the instruction methods it dispatches, how reliably they land, who signs for them, and the programs it calls into.
Methods, not source
Every instruction carries a selector in its first bytes. Axionex groups the program's instructions by that selector — naming the ones it recognises, listing the rest as raw sel codes — to show the real operation mix.
Sampled, then counted
It reads the 40 most recent signatures for the success rate, then fully decodes a sample of them with getTransaction to tally methods, signers and downstream calls. Anchor self-CPI event logs are filtered out.
Reaches into
A protocol rarely acts alone. The downstream panel counts the programs this one invokes by CPI inside the sample — the token programs, pools and routers it leans on to do its job.