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: 8c084bac4d0d102d9e471d58a336f8397afc63cfdc87614362fe0bb1e0cc7f3b
Tx prefix hash: c8706a2ba2645a16f977ee2f6c4f1cc35e2e70369085cd2fbc07ead1fd4507db
Tx public key: 40b2352b1d85c76800a7849e49b5454b66090c356d0e5b46cca33ecceb8ec179
| Timestamp: 1780010829 | Timestamp [UTC]: 2026-05-28 23:27:09 | Age [y:d:h:m:s]: 00:011:02:08:48 |
| Block: 4095 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3791 | RingCT/type: yes/0 |
| Extra: 0140b2352b1d85c76800a7849e49b5454b66090c356d0e5b46cca33ecceb8ec17902090000000326697be300 | ||
1 output(s) for total of 34.910698046588 HMNY
| stealth address | amount | amount idx | tag |
| 00: 07d8ce3f944d0688a3fb968cc00496258c3d70564339e93db80de7dd4db94ba5 | 34.910698046588 | 5096 of 0 | <05> |
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": 4155,
"vin": [ {
"gen": {
"height": 4095
}
}
],
"vout": [ {
"amount": 34910698046588,
"target": {
"tagged_key": {
"key": "07d8ce3f944d0688a3fb968cc00496258c3d70564339e93db80de7dd4db94ba5",
"view_tag": "05"
}
}
}
],
"extra": [ 1, 64, 178, 53, 43, 29, 133, 199, 104, 0, 167, 132, 158, 73, 181, 69, 75, 102, 9, 12, 53, 109, 14, 91, 70, 204, 163, 62, 204, 235, 142, 193, 121, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}