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: 7f5f117edba994a12d8c0c0a5d61b6d8f0e75fb1a69d8ecebad444c96b86f1b0
Tx prefix hash: a2ab1f875f2934e1e61bd79e827e52f9607b824a4273c283640b8fd7f0b8dac1
Tx public key: 735f7d447ef5125a912128cc6b08b8981c521985e87ef36d5eabd0e53076d810
| Timestamp: 1781017583 | Timestamp [UTC]: 2026-06-09 15:06:23 | Age [y:d:h:m:s]: 00:006:03:08:19 |
| Block: 8651 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 94 | RingCT/type: yes/0 |
| Extra: 01735f7d447ef5125a912128cc6b08b8981c521985e87ef36d5eabd0e53076d810020900000001e49593ff00 | ||
1 output(s) for total of 34.608642283837 HMNY
| stealth address | amount | amount idx | tag |
| 00: 6249497333e7a7216dcb071d291d361943fd8965642dd2a20cf0544021b05e9e | 34.608642283837 | 10695 of 0 | <40> |
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": 8711,
"vin": [ {
"gen": {
"height": 8651
}
}
],
"vout": [ {
"amount": 34608642283837,
"target": {
"tagged_key": {
"key": "6249497333e7a7216dcb071d291d361943fd8965642dd2a20cf0544021b05e9e",
"view_tag": "40"
}
}
}
],
"extra": [ 1, 115, 95, 125, 68, 126, 245, 18, 90, 145, 33, 40, 204, 107, 8, 184, 152, 28, 82, 25, 133, 232, 126, 243, 109, 94, 171, 208, 229, 48, 118, 216, 16, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}