Solana instructions › Solana native program instruction indexes
Not every Solana program uses an 8-byte Anchor discriminator. Several core programs ship with the chain and use a small integer tag, encoded as little-endian bytes at the start of the instruction data.
u32. Transfer is 2, so the data starts with 0x02000000. CreateAccount is 0, Assign is 1, and so on, following the SystemInstruction enum.0x02; SetComputeUnitPrice is 0x03. These instructions take no accounts.0x03; TransferChecked is 0x0c). Token-2022 extension instructions add a second u8: TransferCheckedWithFee is 0x1a01.0x00; CreateIdempotent is 0x01.Because a 1-byte tag is only 256 possible values and many programs start their list at 0, 0x00 or 0x02 alone is not enough to name an instruction. Always take the program ID with the tag. Older programs such as Serum DEX v3 and Raydium AMM v4 also use custom layouts; this snapshot lists their instruction names and accounts from the IDL, but does not invent an 8-byte Anchor prefix for them.
Related: How Anchor instruction discriminators work and the instruction decoder.
To see which instructions a confirmed transaction actually ran, paste its signature into the Rugsight transaction explainer.
Instruction lists and published discriminators come from solana-idls@1.2.1 (MIT) and, for the System Program, Compute Budget and Associated Token Account programs, from their public instruction enums (Apache-2.0). Snapshot date 2026-11-17. Programs can upgrade, so a live program may differ from this snapshot. Computed Anchor discriminators are the first 8 bytes of sha256("global:<snake_case_name>") and are labelled as computed.