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: 2dbe4a188b9355daa9dfa7a1a9ee7bfcf4f950b005cd091b140cc9b12c7afc90
Tx prefix hash: b4b1035f9c5d19d7dc77c9be9d476dacbf49c5760c78981ffcb17abca3301f64
Tx public key: aedf5051e497271dd9282f33d7392de851c868ab0bdefc51f63ba0899b2eca9f
| Timestamp: 1779804929 | Timestamp [UTC]: 2026-05-26 14:15:29 | Age [y:d:h:m:s]: 00:013:13:23:21 |
| Block: 2341 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5600 | RingCT/type: yes/0 |
| Extra: 01aedf5051e497271dd9282f33d7392de851c868ab0bdefc51f63ba0899b2eca9f02090000000126697be300 | ||
1 output(s) for total of 35.027687115714 HMNY
| stealth address | amount | amount idx | tag |
| 00: 534f2c034605d06e06720a9cff3a99ac97e9192b63abeaad289cf7dd3c9d9cb5 | 35.027687115714 | 2739 of 0 | <65> |
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": 2401,
"vin": [ {
"gen": {
"height": 2341
}
}
],
"vout": [ {
"amount": 35027687115714,
"target": {
"tagged_key": {
"key": "534f2c034605d06e06720a9cff3a99ac97e9192b63abeaad289cf7dd3c9d9cb5",
"view_tag": "65"
}
}
}
],
"extra": [ 1, 174, 223, 80, 81, 228, 151, 39, 29, 217, 40, 47, 51, 215, 57, 45, 232, 81, 200, 104, 171, 11, 222, 252, 81, 246, 59, 160, 137, 155, 46, 202, 159, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}