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: c5618dfffbfdaa2f1a3f113a8e3eba6bcaaca0c19caf893633b96bdc70666b66
Tx prefix hash: cddb32436418ccdc40449acea63a1fd71b14843353a618616e979cc0d79355f8
Tx public key: fcd9a1ffcef091a19129acc838bdc7b8828c2eb18b61c3fb1c197ad8a195c53c
| Timestamp: 1779869863 | Timestamp [UTC]: 2026-05-27 08:17:43 | Age [y:d:h:m:s]: 00:012:18:32:05 |
| Block: 2784 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5134 | RingCT/type: yes/0 |
| Extra: 01fcd9a1ffcef091a19129acc838bdc7b8828c2eb18b61c3fb1c197ad8a195c53c02090000000226697be300 | ||
1 output(s) for total of 34.998102753064 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8c666eee2603468866ab57567e1409e549c7e9542c0077d89151388e8dc8e038 | 34.998102753064 | 3294 of 0 | <67> |
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": 2844,
"vin": [ {
"gen": {
"height": 2784
}
}
],
"vout": [ {
"amount": 34998102753064,
"target": {
"tagged_key": {
"key": "8c666eee2603468866ab57567e1409e549c7e9542c0077d89151388e8dc8e038",
"view_tag": "67"
}
}
}
],
"extra": [ 1, 252, 217, 161, 255, 206, 240, 145, 161, 145, 41, 172, 200, 56, 189, 199, 184, 130, 140, 46, 177, 139, 97, 195, 251, 28, 25, 122, 216, 161, 149, 197, 60, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}