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: 38cc8bcba682f9c9ec4c032ca22f2a9d99f61cdb8fe3203b3a701838820ce5d3
Tx prefix hash: 803c8c9e6197a4c6fe418893db3b45305892e27c15bd663c66878a6be90e37db
Tx public key: bcd1752c4c0b7e7ac4bf97812f2f54b76d895616283fa1ad00adc755131139d7
| Timestamp: 1780028445 | Timestamp [UTC]: 2026-05-29 04:20:45 | Age [y:d:h:m:s]: 00:019:04:15:29 |
| Block: 4182 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4563 | RingCT/type: yes/0 |
| Extra: 01bcd1752c4c0b7e7ac4bf97812f2f54b76d895616283fa1ad00adc755131139d702090000000326697be300 | ||
1 output(s) for total of 34.904905463805 HMNY
| stealth address | amount | amount idx | tag |
| 00: 6650892c1afae2ab58e6f37c7406189c66ba6aa03498c01b8efa35364da045de | 34.904905463805 | 5215 of 0 | <8a> |
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": 4242,
"vin": [ {
"gen": {
"height": 4182
}
}
],
"vout": [ {
"amount": 34904905463805,
"target": {
"tagged_key": {
"key": "6650892c1afae2ab58e6f37c7406189c66ba6aa03498c01b8efa35364da045de",
"view_tag": "8a"
}
}
}
],
"extra": [ 1, 188, 209, 117, 44, 76, 11, 126, 122, 196, 191, 151, 129, 47, 47, 84, 183, 109, 137, 86, 22, 40, 63, 161, 173, 0, 173, 199, 85, 19, 17, 57, 215, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}