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: 11616aa6ee819249583f180e74f21690c49fc68c88c0139cb0a673ea0f421a42
Tx prefix hash: 5c88425048ba1f472198ab35f7cf7e5e478d643c46ab191e724bf75c02706183
Tx public key: 360324f6b819daf48f32d57b9ebda52346b35b4cf0de32ed3735ed88d1ba045d
| Timestamp: 1780803418 | Timestamp [UTC]: 2026-06-07 03:36:58 | Age [y:d:h:m:s]: 00:001:23:12:50 |
| Block: 6886 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1014 | RingCT/type: yes/0 |
| Extra: 01360324f6b819daf48f32d57b9ebda52346b35b4cf0de32ed3735ed88d1ba045d020900000001e49593ff00 | ||
1 output(s) for total of 34.725347695218 HMNY
| stealth address | amount | amount idx | tag |
| 00: 62df80616924e770ad9fa91ff449099d832ed7d1bc08e1c817ac0ff486ec523d | 34.725347695218 | 8498 of 0 | <63> |
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": 6946,
"vin": [ {
"gen": {
"height": 6886
}
}
],
"vout": [ {
"amount": 34725347695218,
"target": {
"tagged_key": {
"key": "62df80616924e770ad9fa91ff449099d832ed7d1bc08e1c817ac0ff486ec523d",
"view_tag": "63"
}
}
}
],
"extra": [ 1, 54, 3, 36, 246, 184, 25, 218, 244, 143, 50, 213, 123, 158, 189, 165, 35, 70, 179, 91, 76, 240, 222, 50, 237, 55, 53, 237, 136, 209, 186, 4, 93, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}