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: 9fea80968acf41fb68e0c638f331e26e09a0213d2fb0cf5c23cb375d0f24f47c
Tx prefix hash: 3ae55bcc05183867bdaa0a860f08666849b187b945fbb0047871b0aca6f52f45
Tx public key: 668d83973125d355565b628c7dc4704bf8273346f5c7fa12e805d146a08a0330
| Timestamp: 1780694621 | Timestamp [UTC]: 2026-06-05 21:23:41 | Age [y:d:h:m:s]: 00:007:13:38:35 |
| Block: 5951 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2794 | RingCT/type: yes/0 |
| Extra: 01668d83973125d355565b628c7dc4704bf8273346f5c7fa12e805d146a08a0330020900000001e49593ff00 | ||
1 output(s) for total of 34.787331184742 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0f6378322320a2ef53257b3f7d1835a4838994faaf421a145c1b3454efdacac6 | 34.787331184742 | 7414 of 0 | <ae> |
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": 6011,
"vin": [ {
"gen": {
"height": 5951
}
}
],
"vout": [ {
"amount": 34787331184742,
"target": {
"tagged_key": {
"key": "0f6378322320a2ef53257b3f7d1835a4838994faaf421a145c1b3454efdacac6",
"view_tag": "ae"
}
}
}
],
"extra": [ 1, 102, 141, 131, 151, 49, 37, 211, 85, 86, 91, 98, 140, 125, 196, 112, 75, 248, 39, 51, 70, 245, 199, 250, 18, 232, 5, 209, 70, 160, 138, 3, 48, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}