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: 3a9c5b03808a867683ee93b5529537a6c0d3d4e7b9e7f1dfdbef81fb88a21dc5
Tx prefix hash: b21930e5fa74d24c130346618ebb6f940794133c14e1dc202b50b8a92a57231a
Tx public key: a06260d74ba1ea9b8f886a0be02b5080183cc1fc448fa3b65c1f2e563beede3f
| Timestamp: 1780902395 | Timestamp [UTC]: 2026-06-08 07:06:35 | Age [y:d:h:m:s]: 00:000:16:12:18 |
| Block: 7832 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 54 | RingCT/type: yes/0 |
| Extra: 01a06260d74ba1ea9b8f886a0be02b5080183cc1fc448fa3b65c1f2e563beede3f0209000000014a728a4c00 | ||
1 output(s) for total of 34.662747385143 HMNY
| stealth address | amount | amount idx | tag |
| 00: 196e3ba2d0dc1006551e7e5a693a3543fbb51e73c131b15b0514c260e018e781 | 34.662747385143 | 9708 of 0 | <e2> |
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": 7892,
"vin": [ {
"gen": {
"height": 7832
}
}
],
"vout": [ {
"amount": 34662747385143,
"target": {
"tagged_key": {
"key": "196e3ba2d0dc1006551e7e5a693a3543fbb51e73c131b15b0514c260e018e781",
"view_tag": "e2"
}
}
}
],
"extra": [ 1, 160, 98, 96, 215, 75, 161, 234, 155, 143, 136, 106, 11, 224, 43, 80, 128, 24, 60, 193, 252, 68, 143, 163, 182, 92, 31, 46, 86, 59, 238, 222, 63, 2, 9, 0, 0, 0, 1, 74, 114, 138, 76, 0
],
"rct_signatures": {
"type": 0
}
}