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: 751d83274227231d7c9911c5b231308507c8ebf060369a4647c5303790f3e180
Tx prefix hash: 81db623e7a41f09b46b030d1d82b8cddb4effd78bde41ef5419fa5b95f969fb7
Tx public key: ad9698fb8a5adb694b4e0a4454aa0d5cd96aa318adf395c743bca3d71a44d6ec
| Timestamp: 1779781618 | Timestamp [UTC]: 2026-05-26 07:46:58 | Age [y:d:h:m:s]: 00:013:20:04:00 |
| Block: 2114 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5853 | RingCT/type: yes/0 |
| Extra: 01ad9698fb8a5adb694b4e0a4454aa0d5cd96aa318adf395c743bca3d71a44d6ec02090000000226697be300 | ||
1 output(s) for total of 35.042856286354 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8ff44ad6a03f11a7a9650fcdf37c4e4ac7dbd7ba19915362051de0843ca50409 | 35.042856286354 | 2434 of 0 | <6f> |
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": 2174,
"vin": [ {
"gen": {
"height": 2114
}
}
],
"vout": [ {
"amount": 35042856286354,
"target": {
"tagged_key": {
"key": "8ff44ad6a03f11a7a9650fcdf37c4e4ac7dbd7ba19915362051de0843ca50409",
"view_tag": "6f"
}
}
}
],
"extra": [ 1, 173, 150, 152, 251, 138, 90, 219, 105, 75, 78, 10, 68, 84, 170, 13, 92, 217, 106, 163, 24, 173, 243, 149, 199, 67, 188, 163, 215, 26, 68, 214, 236, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}