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: 24a43442c61a6914fdd2102643fc3c37f8cea1d63205d6a2c504633aa0315bf2
Tx prefix hash: a500724d5f5b138b421be592c2831486c4431353cffd46eeab2fe0fb8998cf88
Tx public key: 629da8ecbc1f42a6219185a6979490fe844f60c113839bdf1bc1374a2de0f59c
| Timestamp: 1779464388 | Timestamp [UTC]: 2026-05-22 15:39:48 | Age [y:d:h:m:s]: 00:017:09:06:59 |
| Block: 485 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7401 | RingCT/type: yes/0 |
| Extra: 01629da8ecbc1f42a6219185a6979490fe844f60c113839bdf1bc1374a2de0f59c02090000000293369e7d00 | ||
1 output(s) for total of 35.151906355593 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5ca94a4c89eaac359d9a1080d526c2e993a198c852414af082fe88cc2f4a42c5 | 35.151906355593 | 489 of 0 | <51> |
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": 545,
"vin": [ {
"gen": {
"height": 485
}
}
],
"vout": [ {
"amount": 35151906355593,
"target": {
"tagged_key": {
"key": "5ca94a4c89eaac359d9a1080d526c2e993a198c852414af082fe88cc2f4a42c5",
"view_tag": "51"
}
}
}
],
"extra": [ 1, 98, 157, 168, 236, 188, 31, 66, 166, 33, 145, 133, 166, 151, 148, 144, 254, 132, 79, 96, 193, 19, 131, 155, 223, 27, 193, 55, 74, 45, 224, 245, 156, 2, 9, 0, 0, 0, 2, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}