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: f3d954c25f10dcb60af576f960fa61f9550742ffbd6d8f838686102cb9dbc8ac
Tx prefix hash: 73691d5c2a15a29209b621112a29cec1ca7d6bfca5422c937f84648de049d14c
Tx public key: c241c07446e6216f521b81035c706f42826bcc902de71597ec3ea97a1ff42ebb
| Timestamp: 1779433681 | Timestamp [UTC]: 2026-05-22 07:08:01 | Age [y:d:h:m:s]: 00:017:19:32:35 |
| Block: 55 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0908 kB |
| Tx version: 2 | No of confirmations: 7841 | RingCT/type: yes/0 |
| Extra: 01c241c07446e6216f521b81035c706f42826bcc902de71597ec3ea97a1ff42ebb020900000001a662ed0300 | ||
1 output(s) for total of 35.180748393451 HMNY
| stealth address | amount | amount idx | tag |
| 00: ec8c29e1487160511bff19015e16648ae81f7f65a63445151140a563d31e3887 | 35.180748393451 | 51 of 0 | <4f> |
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": 115,
"vin": [ {
"gen": {
"height": 55
}
}
],
"vout": [ {
"amount": 35180748393451,
"target": {
"tagged_key": {
"key": "ec8c29e1487160511bff19015e16648ae81f7f65a63445151140a563d31e3887",
"view_tag": "4f"
}
}
}
],
"extra": [ 1, 194, 65, 192, 116, 70, 230, 33, 111, 82, 27, 129, 3, 92, 112, 111, 66, 130, 107, 204, 144, 45, 231, 21, 151, 236, 62, 169, 122, 31, 244, 46, 187, 2, 9, 0, 0, 0, 1, 166, 98, 237, 3, 0
],
"rct_signatures": {
"type": 0
}
}