For RingCT transactions, outputs' amounts are also decoded
Tx private key can be obtained using get_tx_key
command in hashmonkey-wallet-cli command line tool
Tx hash: f59f0d155160e6166dfa1c386618e65b2093ea9ff30a046d519141a0dd663f83
Tx prefix hash: 46af6a73f703a98200174896b035c9f4f9a9be4952c35bd741595d80cea88334
Tx public key: 2dea3d3b85a58db41ee0827633e155dbe77c9c23bb872e424171bc2a12ab02fb
| Timestamp: 1780757476 | Timestamp [UTC]: 2026-06-06 14:51:16 | Age [y:d:h:m:s]: 00:002:11:49:20 |
| Block: 6546 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1351 | RingCT/type: yes/0 |
| Extra: 012dea3d3b85a58db41ee0827633e155dbe77c9c23bb872e424171bc2a12ab02fb020900000004e49593ff00 | ||
1 output(s) for total of 34.747874357279 HMNY
| stealth address | amount | amount idx | tag |
| 00: d9dff549dc3f8533ceb3f509c24889fd4017b3c736a29feb7311cc713ace1d20 | 34.747874357279 | 8056 of 0 | <08> |
Check which outputs belong to given HMNY address/subaddress and viewkey
For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side
Prove to someone that you have sent them HMNY in this transaction
Tx private key can be obtained using get_tx_key
command in hashmonkey-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side
{
"version": 2,
"unlock_time": 6606,
"vin": [ {
"gen": {
"height": 6546
}
}
],
"vout": [ {
"amount": 34747874357279,
"target": {
"tagged_key": {
"key": "d9dff549dc3f8533ceb3f509c24889fd4017b3c736a29feb7311cc713ace1d20",
"view_tag": "08"
}
}
}
],
"extra": [ 1, 45, 234, 61, 59, 133, 165, 141, 180, 30, 224, 130, 118, 51, 225, 85, 219, 231, 124, 156, 35, 187, 135, 46, 66, 65, 113, 188, 42, 18, 171, 2, 251, 2, 9, 0, 0, 0, 4, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}