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: 9e4fb2f43758356613015a301764a6cb027d14e3f10962621b38b5d61e8e5a55
Tx prefix hash: 782c5f4c48b8eefe4d61191c489c3e7d533cfb0e0c5af98474fddc95dae0d392
Tx public key: a94e799846768ab5c91f4c5b2b0e89e5cf599bf99fe6d9b88258c56401ca40c9
| Timestamp: 1780983448 | Timestamp [UTC]: 2026-06-09 05:37:28 | Age [y:d:h:m:s]: 00:000:04:32:35 |
| Block: 8090 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 336 | RingCT/type: yes/0 |
| Extra: 01a94e799846768ab5c91f4c5b2b0e89e5cf599bf99fe6d9b88258c56401ca40c9020900000002e49593ff00 | ||
1 output(s) for total of 34.645694167624 HMNY
| stealth address | amount | amount idx | tag |
| 00: 077374840d2b8f851b372435a6c21bbdc4742403603f0720e3f4ce9614371677 | 34.645694167624 | 10022 of 0 | <93> |
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": 8150,
"vin": [ {
"gen": {
"height": 8090
}
}
],
"vout": [ {
"amount": 34645694167624,
"target": {
"tagged_key": {
"key": "077374840d2b8f851b372435a6c21bbdc4742403603f0720e3f4ce9614371677",
"view_tag": "93"
}
}
}
],
"extra": [ 1, 169, 78, 121, 152, 70, 118, 138, 181, 201, 31, 76, 91, 43, 14, 137, 229, 207, 89, 155, 249, 159, 230, 217, 184, 130, 88, 197, 100, 1, 202, 64, 201, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}