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: 7936b2177504631b37cb902726aa2a8c08030ce118dae5b68b925f1289325e16
Tx prefix hash: 9ad222478e97f6d9bd4537524a615f1e9168d7c1739e5fc739fb7332a3c73c68
Tx public key: 3ba0a05ab3d838792f3365d0b271d8547194a25685807f088dddc8dddc8d4fac
| Timestamp: 1779918971 | Timestamp [UTC]: 2026-05-27 21:56:11 | Age [y:d:h:m:s]: 00:012:04:44:25 |
| Block: 3343 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4554 | RingCT/type: yes/0 |
| Extra: 013ba0a05ab3d838792f3365d0b271d8547194a25685807f088dddc8dddc8d4fac02090000000926697be300 | ||
1 output(s) for total of 34.960807350214 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4ca08763611f2f4b512193459a75c80fe57fb247c8e9bf804d246e5e3aec51ad | 34.960807350214 | 4018 of 0 | <10> |
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": 3403,
"vin": [ {
"gen": {
"height": 3343
}
}
],
"vout": [ {
"amount": 34960807350214,
"target": {
"tagged_key": {
"key": "4ca08763611f2f4b512193459a75c80fe57fb247c8e9bf804d246e5e3aec51ad",
"view_tag": "10"
}
}
}
],
"extra": [ 1, 59, 160, 160, 90, 179, 216, 56, 121, 47, 51, 101, 208, 178, 113, 216, 84, 113, 148, 162, 86, 133, 128, 127, 8, 141, 221, 200, 221, 220, 141, 79, 172, 2, 9, 0, 0, 0, 9, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}