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: 062ff15df777f6784040f73573823039ac73da7f080b85b5add26112dc332b55
Tx prefix hash: 2273c10f63c667758358d7c5ad53b77d9535c4f55ecaef8bec635a3803962e51
Tx public key: 041ef1517a03e86aa868e45cab9aced2e8fa459947f4de2ada636e9a8639768b
| Timestamp: 1779843635 | Timestamp [UTC]: 2026-05-27 01:00:35 | Age [y:d:h:m:s]: 00:012:23:46:12 |
| Block: 2426 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5460 | RingCT/type: yes/0 |
| Extra: 01041ef1517a03e86aa868e45cab9aced2e8fa459947f4de2ada636e9a8639768b02090000000226697be300 | ||
1 output(s) for total of 35.022008719669 HMNY
| stealth address | amount | amount idx | tag |
| 00: 126d43eb5306bf5c0c56c4b2908dbc8437408b72d28ca99e948dade7c430519d | 35.022008719669 | 2850 of 0 | <df> |
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": 2486,
"vin": [ {
"gen": {
"height": 2426
}
}
],
"vout": [ {
"amount": 35022008719669,
"target": {
"tagged_key": {
"key": "126d43eb5306bf5c0c56c4b2908dbc8437408b72d28ca99e948dade7c430519d",
"view_tag": "df"
}
}
}
],
"extra": [ 1, 4, 30, 241, 81, 122, 3, 232, 106, 168, 104, 228, 92, 171, 154, 206, 210, 232, 250, 69, 153, 71, 244, 222, 42, 218, 99, 110, 154, 134, 57, 118, 139, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}