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: 36b80285343554bff58938bfa877d5d42d74438aba913e4a257626b17955ef0a
Tx prefix hash: dff4b2107bf0f1358b191af1a9aa27753d83a7e85eb1babf42a5c0816b623830
Tx public key: f2e8803db020a9e57fb6b4d3cdb72be79245a0979f1a0939ad9207b512138928
| Timestamp: 1779636291 | Timestamp [UTC]: 2026-05-24 15:24:51 | Age [y:d:h:m:s]: 00:015:10:11:06 |
| Block: 1102 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6784 | RingCT/type: yes/0 |
| Extra: 01f2e8803db020a9e57fb6b4d3cdb72be79245a0979f1a0939ad9207b512138928020900000001ba6d17be00 | ||
1 output(s) for total of 35.110562685951 HMNY
| stealth address | amount | amount idx | tag |
| 00: 596818eb2ced909d72373edf753c45ee598866453c5553dc8d9ab97367cff01e | 35.110562685951 | 1242 of 0 | <06> |
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": 1162,
"vin": [ {
"gen": {
"height": 1102
}
}
],
"vout": [ {
"amount": 35110562685951,
"target": {
"tagged_key": {
"key": "596818eb2ced909d72373edf753c45ee598866453c5553dc8d9ab97367cff01e",
"view_tag": "06"
}
}
}
],
"extra": [ 1, 242, 232, 128, 61, 176, 32, 169, 229, 127, 182, 180, 211, 205, 183, 43, 231, 146, 69, 160, 151, 159, 26, 9, 57, 173, 146, 7, 181, 18, 19, 137, 40, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}