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: 91fb8dd1cd5b345631e1f1fc0c0d8717ab7f444ff9866842836f0e091c5e0e6e
Tx prefix hash: c3518f71f76c19ac634532aa32a01d413c7f992e6fec3045f6569bd903e72fb0
Tx public key: cbf9ff76e93f7b0dc0b4d82b53f59c17932fca9c7d48e87b0a94e9910d637ee4
| Timestamp: 1780997842 | Timestamp [UTC]: 2026-06-09 09:37:22 | Age [y:d:h:m:s]: 00:000:06:22:22 |
| Block: 8383 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 308 | RingCT/type: yes/0 |
| Extra: 01cbf9ff76e93f7b0dc0b4d82b53f59c17932fca9c7d48e87b0a94e9910d637ee4020900000001e49593ff00 | ||
1 output(s) for total of 34.626337703080 HMNY
| stealth address | amount | amount idx | tag |
| 00: 826e995208c15648073000b6828243a3f39a42553ea425f01a48c568477b06d9 | 34.626337703080 | 10363 of 0 | <3a> |
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": 8443,
"vin": [ {
"gen": {
"height": 8383
}
}
],
"vout": [ {
"amount": 34626337703080,
"target": {
"tagged_key": {
"key": "826e995208c15648073000b6828243a3f39a42553ea425f01a48c568477b06d9",
"view_tag": "3a"
}
}
}
],
"extra": [ 1, 203, 249, 255, 118, 233, 63, 123, 13, 192, 180, 216, 43, 83, 245, 156, 23, 147, 47, 202, 156, 125, 72, 232, 123, 10, 148, 233, 145, 13, 99, 126, 228, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}