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: 79ccc20b2f7725e4f8cf7d51e854f79853a7a9a6f0db470dbd9e5a7adc0ba9a6
Tx prefix hash: c49da72e1dbbfac09120fa8421b1e8152ad6ff070dcbfcb6d0d6d9fcf28b41f3
Tx public key: 96e801cff0000bc109a57d5b558e67ffdcb0c1768d1c2ea06f36a6fe52ed88a1
| Timestamp: 1780893598 | Timestamp [UTC]: 2026-06-08 04:39:58 | Age [y:d:h:m:s]: 00:000:20:06:49 |
| Block: 7751 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 135 | RingCT/type: yes/0 |
| Extra: 0196e801cff0000bc109a57d5b558e67ffdcb0c1768d1c2ea06f36a6fe52ed88a10209000000044a728a4c00 | ||
1 output(s) for total of 34.679531833402 HMNY
| stealth address | amount | amount idx | tag |
| 00: 68d5587dd2944d5849b53d7fc55374630f179489835571183fa5d01a0adb170c | 34.679531833402 | 9595 of 0 | <af> |
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": 7811,
"vin": [ {
"gen": {
"height": 7751
}
}
],
"vout": [ {
"amount": 34679531833402,
"target": {
"tagged_key": {
"key": "68d5587dd2944d5849b53d7fc55374630f179489835571183fa5d01a0adb170c",
"view_tag": "af"
}
}
}
],
"extra": [ 1, 150, 232, 1, 207, 240, 0, 11, 193, 9, 165, 125, 91, 85, 142, 103, 255, 220, 176, 193, 118, 141, 28, 46, 160, 111, 54, 166, 254, 82, 237, 136, 161, 2, 9, 0, 0, 0, 4, 74, 114, 138, 76, 0
],
"rct_signatures": {
"type": 0
}
}