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: d6be4f16e7573e12b33e2c2e6f57adc422304404626046f430df87fb799c7250
Tx prefix hash: ec7b2d1a792ab3737040a02a8a34a3a89d28786436f6e5893f4bdcb4d29a7f4c
Tx public key: 1877046cc5e89509406f2bd1e74f7c10ece9603dbd60f4bf0457e55a4eeec049
| Timestamp: 1779434709 | Timestamp [UTC]: 2026-05-22 07:25:09 | Age [y:d:h:m:s]: 00:017:19:24:39 |
| Block: 99 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0918 kB |
| Tx version: 2 | No of confirmations: 7821 | RingCT/type: yes/0 |
| Extra: 011877046cc5e89509406f2bd1e74f7c10ece9603dbd60f4bf0457e55a4eeec049020900000001a662ed0300 | ||
1 output(s) for total of 35.177796028620 HMNY
| stealth address | amount | amount idx | tag |
| 00: 1d2e800918b24ac55608ccf355e74dc8a53987f9310bd3823bfd7cf571723314 | 35.177796028620 | 95 of 0 | <9c> |
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": 159,
"vin": [ {
"gen": {
"height": 99
}
}
],
"vout": [ {
"amount": 35177796028620,
"target": {
"tagged_key": {
"key": "1d2e800918b24ac55608ccf355e74dc8a53987f9310bd3823bfd7cf571723314",
"view_tag": "9c"
}
}
}
],
"extra": [ 1, 24, 119, 4, 108, 197, 232, 149, 9, 64, 111, 43, 209, 231, 79, 124, 16, 236, 233, 96, 61, 189, 96, 244, 191, 4, 87, 229, 90, 78, 238, 192, 73, 2, 9, 0, 0, 0, 1, 166, 98, 237, 3, 0
],
"rct_signatures": {
"type": 0
}
}