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: a0e9acef67e5362b9bf2c9b4bebe8a5b694a0eba9304d0c0a0dd8b97c6fb9e53
Tx prefix hash: b7d9f05b3627070a305b6a1a8b6ab7a7d37252dc5bf6190183cfdf0553e5262a
Tx public key: bc49899c3583cd3a56350f55d2a7113fd72a8142e9fad3ae1004390b1af20fea
| Timestamp: 1779631797 | Timestamp [UTC]: 2026-05-24 14:09:57 | Age [y:d:h:m:s]: 00:015:12:30:39 |
| Block: 924 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6972 | RingCT/type: yes/0 |
| Extra: 01bc49899c3583cd3a56350f55d2a7113fd72a8142e9fad3ae1004390b1af20fea020900000001ba6d17be00 | ||
1 output(s) for total of 35.122485039979 HMNY
| stealth address | amount | amount idx | tag |
| 00: 06348cc03a70f8059b3818aa01f2153b8c582cda48e1576cb94845535f2fc4c3 | 35.122485039979 | 1058 of 0 | <57> |
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": 984,
"vin": [ {
"gen": {
"height": 924
}
}
],
"vout": [ {
"amount": 35122485039979,
"target": {
"tagged_key": {
"key": "06348cc03a70f8059b3818aa01f2153b8c582cda48e1576cb94845535f2fc4c3",
"view_tag": "57"
}
}
}
],
"extra": [ 1, 188, 73, 137, 156, 53, 131, 205, 58, 86, 53, 15, 85, 210, 167, 17, 63, 215, 42, 129, 66, 233, 250, 211, 174, 16, 4, 57, 11, 26, 242, 15, 234, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}