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: a2fd558f89e52652b79e3d0d2533b27d144a8469d14b6696a44b45836848642b
Tx prefix hash: 458dfd912bdb8dd72257f45fdee3e9289d4c05b7d4ae85397bfce83cfaee9aef
Tx public key: 9ac52f7fb8e30afbe132c3bb18711342b65b5f7698876a485f74fda5b8b06af3
| Timestamp: 1779895681 | Timestamp [UTC]: 2026-05-27 15:28:01 | Age [y:d:h:m:s]: 00:012:10:07:56 |
| Block: 3103 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4783 | RingCT/type: yes/0 |
| Extra: 019ac52f7fb8e30afbe132c3bb18711342b65b5f7698876a485f74fda5b8b06af302090000000426697be300 | ||
1 output(s) for total of 34.976814816563 HMNY
| stealth address | amount | amount idx | tag |
| 00: 69bb95b727206f398cbeb3888ff4fde17bef8d837f1ac2157c305b3caf91018c | 34.976814816563 | 3699 of 0 | <83> |
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": 3163,
"vin": [ {
"gen": {
"height": 3103
}
}
],
"vout": [ {
"amount": 34976814816563,
"target": {
"tagged_key": {
"key": "69bb95b727206f398cbeb3888ff4fde17bef8d837f1ac2157c305b3caf91018c",
"view_tag": "83"
}
}
}
],
"extra": [ 1, 154, 197, 47, 127, 184, 227, 10, 251, 225, 50, 195, 187, 24, 113, 19, 66, 182, 91, 95, 118, 152, 135, 106, 72, 95, 116, 253, 165, 184, 176, 106, 243, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}