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: b4384f2fde46b0dee68545012981c6dbf79a6b9dd4552f553c34c6fa4b056a2a
Tx prefix hash: 7d1db7bd049171e2fa75a336609ecde142b6707c529edf4c40c09650c9190e1c
Tx public key: 6ffb1b5971ea1154c1541736b66b128ab6c46852716cb9fc445dfa968572d6f2
| Timestamp: 1779871618 | Timestamp [UTC]: 2026-05-27 08:46:58 | Age [y:d:h:m:s]: 00:012:18:51:52 |
| Block: 2817 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5125 | RingCT/type: yes/0 |
| Extra: 016ffb1b5971ea1154c1541736b66b128ab6c46852716cb9fc445dfa968572d6f202090000000126697be300 | ||
1 output(s) for total of 34.995899952035 HMNY
| stealth address | amount | amount idx | tag |
| 00: f18a56e451e88a512010af26e477ff735b380608064461f6892618d9bd1b0e43 | 34.995899952035 | 3333 of 0 | <6c> |
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": 2877,
"vin": [ {
"gen": {
"height": 2817
}
}
],
"vout": [ {
"amount": 34995899952035,
"target": {
"tagged_key": {
"key": "f18a56e451e88a512010af26e477ff735b380608064461f6892618d9bd1b0e43",
"view_tag": "6c"
}
}
}
],
"extra": [ 1, 111, 251, 27, 89, 113, 234, 17, 84, 193, 84, 23, 54, 182, 107, 18, 138, 182, 196, 104, 82, 113, 108, 185, 252, 68, 93, 250, 150, 133, 114, 214, 242, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}