NOTES:

When a Solana Program IDL is public, the easiest approach is to submit the IDL to Flipside.

It will decode all the instructions and we can easily look at the data in the solana.core.ez_events_decoded table.

In cases where the IDL is not public, but the devs were considerate enough to log detailed data, this is what i use at the start of my decoding journey.

Parameters:

• program_address

  • address of the target program

• lookback_days

  • how many days to look back for transactions

IDL Sumit Link:

• https://science.flipsidecrypto.xyz/idl-requestor/

1. instruction_name : Instruction as named in the transaction log

2. log_references : count of times the instruction names shows up in logs

3. instruction_hex_indentifier: 16 hexadecimal characters that identify the instruction being called (fetched from instructions:data)

4. first_log_reference: FIRST transaction timestamp where the instruction name is referenced in the logs

5. last_log_reference: LAST transaction timestamp where the instruction name is referenced in the logs

6. sample_tx: a random transaction id where this instruction is referenced

7. sample_instruction: a random tx instruction. (might not match the sample_tx instruction)

8. sample_inner_instruction: a random inner instruction (might not match the sample_tx inner instructions)

9. sample_instruction_data: random full instruction data (base58) (might not match the sample_tx instruction data)