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: a1005ed845f36544080d702807ae4858282d6e5b8b3862fd83ea630506f038b4
Tx prefix hash: 2cd355e6a71b58556bb2973daf250897161608778cc11a730657a16b268a3ec6
Tx public key: cd05849840eef4721a8a37e0aa02312d0f424744e640a932d7a960eacc01677c
| Timestamp: 1780681621 | Timestamp [UTC]: 2026-06-05 17:47:01 | Age [y:d:h:m:s]: 00:003:03:25:06 |
| Block: 5291 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2595 | RingCT/type: yes/0 |
| Extra: 01cd05849840eef4721a8a37e0aa02312d0f424744e640a932d7a960eacc01677c020900000003e49593ff00 | ||
1 output(s) for total of 34.831150837191 HMNY
| stealth address | amount | amount idx | tag |
| 00: 686f163d886afcec8a704330e9e438eb04183c59918d303e39373d7caeade57e | 34.831150837191 | 6714 of 0 | <73> |
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": 5351,
"vin": [ {
"gen": {
"height": 5291
}
}
],
"vout": [ {
"amount": 34831150837191,
"target": {
"tagged_key": {
"key": "686f163d886afcec8a704330e9e438eb04183c59918d303e39373d7caeade57e",
"view_tag": "73"
}
}
}
],
"extra": [ 1, 205, 5, 132, 152, 64, 238, 244, 114, 26, 138, 55, 224, 170, 2, 49, 45, 15, 66, 71, 68, 230, 64, 169, 50, 215, 169, 96, 234, 204, 1, 103, 124, 2, 9, 0, 0, 0, 3, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}