Aaradhya Textile Industry
Solana: Is there a way to decrypt transactions obtained from getBlock to obtain information such as amount, source, destination?
Decoding SOL Transaction Data
As a developer building applications on Solana, you’re likely interested in parsing the data fetched from 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
receiver: '0x9876543210fedcba', // recipient address
data: { amount: 100, fee: 10 }, // transaction data
gasPrice: 1e8, // transaction gas price
gasLimit: 200000, // transaction gas limit
},
output: {
receiver: '0x9876543210fedcba', // recipient address
amount: 100,
fee: 10,
},
};
In this example, we have an splProgram transaction with two inputs (sender and receiver) and three outputs (amount, fee, and gasPrice). We can access their values using dot notation.
SPL Program Transactions
SPL program transactions are similar to SOL program transactions but differ in syntax. You’ll need to use the splProgramInput object instead of splProgram.
Example: Solana Transaction Data (SPL)
const tx = {
type: 'splProgram',
input: {
sender: { address: '0x1234567890abcdef', pubkeyHash: '0x1234567890abcdef' },
receiver: { address: '0x9876543210fedcba', pubkeyHash: '0x9876543210fedcba' },
data: { amount: 100, fee: 10 }, // transaction data
gasPrice: 1e8,
gasLimit: 200000, // transaction gas limit
},
output: {
receiver: { 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 features or creating custom functions to parse the data. By following these examples and tips, you’ll be able to decode transaction data from both native SOL and SPL program transactions on Solana.