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: ba72ed6e953265fa871ebcf4d0fc7b14293ac7a5715878d4f4d087d9832982e6
Tx prefix hash: 9cdeea6a71d5a3183169a43172483e5566832ee6b1863928a5b976dbc5813e41
Tx public key: d03d71692b73e619b4698a5c9545516115581573470b022884e6eede107d00f4
| Timestamp: 1780997848 | Timestamp [UTC]: 2026-06-09 09:37:28 | Age [y:d:h:m:s]: 00:000:06:22:16 |
| Block: 8384 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 307 | RingCT/type: yes/0 |
| Extra: 01d03d71692b73e619b4698a5c9545516115581573470b022884e6eede107d00f4020900000001e49593ff00 | ||
1 output(s) for total of 34.626271658582 HMNY
| stealth address | amount | amount idx | tag |
| 00: 72ee7e9412c2cf433c33fd37221c9757b21573d48d285fc432567b2e30a9db43 | 34.626271658582 | 10364 of 0 | <33> |
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": 8444,
"vin": [ {
"gen": {
"height": 8384
}
}
],
"vout": [ {
"amount": 34626271658582,
"target": {
"tagged_key": {
"key": "72ee7e9412c2cf433c33fd37221c9757b21573d48d285fc432567b2e30a9db43",
"view_tag": "33"
}
}
}
],
"extra": [ 1, 208, 61, 113, 105, 43, 115, 230, 25, 180, 105, 138, 92, 149, 69, 81, 97, 21, 88, 21, 115, 71, 11, 2, 40, 132, 230, 238, 222, 16, 125, 0, 244, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}