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: 5b4869a2ad511e3c31b0978f9e92c0f0700a1a312556df748e032d6b0f1e0e36
Tx prefix hash: c6cfedaedb05865d17e001b7390d28acaf552f5ea33ab012de7513c2f76010bb
Tx public key: 6e00b7eb531b69d01f424f91d9039d050fc3cd9980c4e32be1e74228033a1a19
| Timestamp: 1780854845 | Timestamp [UTC]: 2026-06-07 17:54:05 | Age [y:d:h:m:s]: 00:001:03:18:02 |
| Block: 7562 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 324 | RingCT/type: yes/0 |
| Extra: 016e00b7eb531b69d01f424f91d9039d050fc3cd9980c4e32be1e74228033a1a19020900000004e49593ff00 | ||
1 output(s) for total of 34.680602764230 HMNY
| stealth address | amount | amount idx | tag |
| 00: 10b34fecded1aad8b09fe6cf890f435adbe7fc08fe8d96bd34b3710859846db8 | 34.680602764230 | 9338 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": 7622,
"vin": [ {
"gen": {
"height": 7562
}
}
],
"vout": [ {
"amount": 34680602764230,
"target": {
"tagged_key": {
"key": "10b34fecded1aad8b09fe6cf890f435adbe7fc08fe8d96bd34b3710859846db8",
"view_tag": "06"
}
}
}
],
"extra": [ 1, 110, 0, 183, 235, 83, 27, 105, 208, 31, 66, 79, 145, 217, 3, 157, 5, 15, 195, 205, 153, 128, 196, 227, 43, 225, 231, 66, 40, 3, 58, 26, 25, 2, 9, 0, 0, 0, 4, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}