Decoding SOL Transaction Data
As a developer building applications on Solana, you’re probably interested in analyzing the data retrieved by gettingBlock to extract specific information about native SOL transactions. In this article, we’ll explore how to decode transaction data from both native SOL and SPL program transactions.
SOL program transactions
SOL program transactions are similar to traditional JavaScript objects. You can access their properties using dot notation (obj.propertyName).
Example: Solana transaction data
const tx = {
Type: "splProgram",
Input: {
Sender: "0x1234567890abcdef", // Sender address
Recipient: "0x9876543210fedcba", // Recipient address
Data: { Amount: 100, Fee: 10 }, // Transaction data
Gas price: 1e8, // Gas price for transaction
Gas limit: 200000, // Gas limit for transaction
},
Output: {
Recipient: "0x9876543210fedcba", // Recipient address
Amount: 100,
Fee: 10,
},
};
In this example, we have a splProgram transaction with two inputs (sender and recipient) and three outputs (amount, fee and gas price). We can get their values using dot notation.
SPL program transactions
SPL program transactions are similar to SOL program transactions, but differ in syntax. You must use the splProgramInput object instead of splProgram.
Example: Solana Transaction Data (SPL)
const tx = {
Type: "splProgram",
Input: {
Sender: { Address: "0x1234567890abcdef", pubkeyHash: "0x1234567890abcdef" },
Recipient: { Address: "0x9876543210fedcba", pubkeyHash: "0x9876543210fedcba" },
Data: { Amount: 100, Fee: 10 }, // Transaction Data
Gas Price: 1e8,
Gas Limit: 200000, // Transaction Gas Limit
},
Output: {
Recipient: { Address: "0x9876543210fedcba", pubkeyHash: '0x9876543210fedcba' },
Amount: 100,
Fee: 10,
},
};
Similar to the SOL example, we have a splProgram transaction with inputs and outputs.
Decoding Transaction Data
To decode transaction data from both native SOL and SPL program transactions, you can use JavaScript’s built-in object destructuring features or create custom functions to parse the data.
Native Sol Example
function parseSolTransaction(tx) {
const sender = tx.input.sender;
const receiver = tx.input.receiver;
const amount = tx.input.data.amount;
const gasPrice = tx.input.data.gasPrice;
return { sender, receiver, amount, gasPrice };
}
const solTx = {
type: 'splProgram',
input: {
sender,
receiver,
data: {
amount,
fee,
gasPrice,
gasLimit,
},
},
output: {},
};
parseSolTransaction(solTx);
In this example, we define a parseSolTransaction function that takes a transaction object and returns an object with the decoded values.
SPL example
function parseSPLTransaction(tx) {
const sender = tx.input.sender;
const receiver = tx.input.receiver;
const amount = tx.output.amount;
const gasPrice = tx.input.data.gasPrice;
return { sender, receiver, amount, gasPrice };
}
const splTx = {
type: 'splProgram',
input: {
sender,
receiver,
},
output: {
receiver,
amount,
fee,
},
};
parseSPLTransaction(splTx);
Similarly, we define a parseSPLTransaction function for SPL program transactions.
Conclusion
Parsing SOL and SPL transaction data can be simplified by using JavaScript’s built-in object destructuring capabilities or by creating custom functions to parse the data. By following these examples and tips, you will be able to decode transaction data from both native SOL and SPL program transactions on Solana.
