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: 4222da5d5876e8568816d3bfb90f32d03890aa4a7fe428f0a7cc8ad39df0e6a9
Tx prefix hash: 16107072185d2ce6a484dff4bd23d5c843cfc1a00aa481947648e23f81928584
Tx public key: 99d79daf844133e8efb8f6a00d2c4edaa2ebd0c480d0aae83f0fe307d9c12e0e
| Timestamp: 1779867929 | Timestamp [UTC]: 2026-05-27 07:45:29 | Age [y:d:h:m:s]: 00:012:17:50:28 |
| Block: 2768 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5118 | RingCT/type: yes/0 |
| Extra: 0199d79daf844133e8efb8f6a00d2c4edaa2ebd0c480d0aae83f0fe307d9c12e0e02090000000326697be300 | ||
1 output(s) for total of 34.999170827715 HMNY
| stealth address | amount | amount idx | tag |
| 00: 469977f5174b6a0e67d696fe4aa966f9606a2c7308e632f9f2db75ff6933202e | 34.999170827715 | 3272 of 0 | <7c> |
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": 2828,
"vin": [ {
"gen": {
"height": 2768
}
}
],
"vout": [ {
"amount": 34999170827715,
"target": {
"tagged_key": {
"key": "469977f5174b6a0e67d696fe4aa966f9606a2c7308e632f9f2db75ff6933202e",
"view_tag": "7c"
}
}
}
],
"extra": [ 1, 153, 215, 157, 175, 132, 65, 51, 232, 239, 184, 246, 160, 13, 44, 78, 218, 162, 235, 208, 196, 128, 208, 170, 232, 63, 15, 227, 7, 217, 193, 46, 14, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}