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: 3a9f5dc994cbee2787d9d4ca2a80263c5bf7a2367c8912f838276ec7ab21fad8
Tx prefix hash: 732799cac3e7a7e0ede0e346ab46270ba79723054c1f5cfb88b80122dd806f15
Tx public key: 5d7069de1caf35902e8a01c7b4287d0ccf70da6a002044425d8539a5182600e4
| Timestamp: 1779645020 | Timestamp [UTC]: 2026-05-24 17:50:20 | Age [y:d:h:m:s]: 00:015:05:28:33 |
| Block: 1438 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6448 | RingCT/type: yes/0 |
| Extra: 015d7069de1caf35902e8a01c7b4287d0ccf70da6a002044425d8539a5182600e4020900000001ba6d17be00 | ||
1 output(s) for total of 35.088068597017 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0eae96784cc9b406cc18bacc97c1c2b28c7f947cfe2f952e6387b1fd29359557 | 35.088068597017 | 1592 of 0 | <b5> |
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": 1498,
"vin": [ {
"gen": {
"height": 1438
}
}
],
"vout": [ {
"amount": 35088068597017,
"target": {
"tagged_key": {
"key": "0eae96784cc9b406cc18bacc97c1c2b28c7f947cfe2f952e6387b1fd29359557",
"view_tag": "b5"
}
}
}
],
"extra": [ 1, 93, 112, 105, 222, 28, 175, 53, 144, 46, 138, 1, 199, 180, 40, 125, 12, 207, 112, 218, 106, 0, 32, 68, 66, 93, 133, 57, 165, 24, 38, 0, 228, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}