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: 427e322a33c1cbe1a65443a7a45a0a8a7e7ef4be3ec3fb8d762ec761e28fd77c
Tx prefix hash: f1deea571580e0d90645694aae631480f548cb4724dd01e0e39fdbfbe4020a79
Tx public key: e9401d137b9ffdef7d0facd530e75a7f903f711f8f4ad4ac1632928e94907801
| Timestamp: 1779635658 | Timestamp [UTC]: 2026-05-24 15:14:18 | Age [y:d:h:m:s]: 00:015:11:35:30 |
| Block: 1084 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6836 | RingCT/type: yes/0 |
| Extra: 01e9401d137b9ffdef7d0facd530e75a7f903f711f8f4ad4ac1632928e94907801020900000001ba6d17be00 | ||
1 output(s) for total of 35.111768133300 HMNY
| stealth address | amount | amount idx | tag |
| 00: 255f3d0520e583d608173aa8e11b80bbe7c40a821d612f3d3be1b8dc398214d0 | 35.111768133300 | 1224 of 0 | <94> |
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": 1144,
"vin": [ {
"gen": {
"height": 1084
}
}
],
"vout": [ {
"amount": 35111768133300,
"target": {
"tagged_key": {
"key": "255f3d0520e583d608173aa8e11b80bbe7c40a821d612f3d3be1b8dc398214d0",
"view_tag": "94"
}
}
}
],
"extra": [ 1, 233, 64, 29, 19, 123, 159, 253, 239, 125, 15, 172, 213, 48, 231, 90, 127, 144, 63, 113, 31, 143, 74, 212, 172, 22, 50, 146, 142, 148, 144, 120, 1, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}