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: 70e1eb21707790d1099360b7ee24fa6605d738bd28b77b7add37e93e5bd921e6
Tx prefix hash: 03185a22f215b2bf7f3275adc15489836d8804616279b990dff8b330859ce439
Tx public key: aefe184935f0749840b930daf0e3914d3db9a5e203900a9046b0c8e9b274478b
| Timestamp: 1779632148 | Timestamp [UTC]: 2026-05-24 14:15:48 | Age [y:d:h:m:s]: 00:015:12:34:00 |
| Block: 938 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6961 | RingCT/type: yes/0 |
| Extra: 01aefe184935f0749840b930daf0e3914d3db9a5e203900a9046b0c8e9b274478b020900000001ba6d17be00 | ||
1 output(s) for total of 35.121547180073 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4fce0025d7e7058a54a0a2c80818a755f33a52e75ab7bca31f327ea4eaf2a90d | 35.121547180073 | 1072 of 0 | <04> |
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": 998,
"vin": [ {
"gen": {
"height": 938
}
}
],
"vout": [ {
"amount": 35121547180073,
"target": {
"tagged_key": {
"key": "4fce0025d7e7058a54a0a2c80818a755f33a52e75ab7bca31f327ea4eaf2a90d",
"view_tag": "04"
}
}
}
],
"extra": [ 1, 174, 254, 24, 73, 53, 240, 116, 152, 64, 185, 48, 218, 240, 227, 145, 77, 61, 185, 165, 226, 3, 144, 10, 144, 70, 176, 200, 233, 178, 116, 71, 139, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}