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: 2d20b6d2f3d9ba984daee1170577a2a43aa5334520dff5ed84984c29b331eaa7
Tx prefix hash: d25c494853f423ca26ba5c39c108e9a9229b58bf4e0a5ff7bb27533ebaad575a
Tx public key: e66f1ffbb2a6dfc3d29cf87c3b25dea2f98df7f2311fa449582d9e3cc8f41e64
| Timestamp: 1779871026 | Timestamp [UTC]: 2026-05-27 08:37:06 | Age [y:d:h:m:s]: 00:013:08:31:57 |
| Block: 2808 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5927 | RingCT/type: yes/0 |
| Extra: 01e66f1ffbb2a6dfc3d29cf87c3b25dea2f98df7f2311fa449582d9e3cc8f41e6402090000000126697be300 | ||
1 output(s) for total of 34.996500702202 HMNY
| stealth address | amount | amount idx | tag |
| 00: d15a00e710c7b62132d946c36fbe3161fa7f3de3618de8cb283644fbd44d192f | 34.996500702202 | 3322 of 0 | <af> |
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": 2868,
"vin": [ {
"gen": {
"height": 2808
}
}
],
"vout": [ {
"amount": 34996500702202,
"target": {
"tagged_key": {
"key": "d15a00e710c7b62132d946c36fbe3161fa7f3de3618de8cb283644fbd44d192f",
"view_tag": "af"
}
}
}
],
"extra": [ 1, 230, 111, 31, 251, 178, 166, 223, 195, 210, 156, 248, 124, 59, 37, 222, 162, 249, 141, 247, 242, 49, 31, 164, 73, 88, 45, 158, 60, 200, 244, 30, 100, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}