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: e269b7711c6138b3631eea8d99507cd3239cdd063ee95a45717d9339f0a8637b
Tx prefix hash: 7542928e46b90f02abf434ed85c1c68c3412786c69718a4f6c4b5cc4c74b8dd0
Tx public key: b01245e9250a74ae47303ca490a8bab75f0b8c7e35eaf823a287ece7d52a882c
| Timestamp: 1779486767 | Timestamp [UTC]: 2026-05-22 21:52:47 | Age [y:d:h:m:s]: 00:017:04:57:01 |
| Block: 662 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7238 | RingCT/type: yes/0 |
| Extra: 01b01245e9250a74ae47303ca490a8bab75f0b8c7e35eaf823a287ece7d52a882c02090000000293369e7d00 | ||
1 output(s) for total of 35.140041038787 HMNY
| stealth address | amount | amount idx | tag |
| 00: d0110db319fc97ef0a599b3d0cf2b36334a2a060f648a7320583195d27c46a36 | 35.140041038787 | 717 of 0 | <5f> |
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": 722,
"vin": [ {
"gen": {
"height": 662
}
}
],
"vout": [ {
"amount": 35140041038787,
"target": {
"tagged_key": {
"key": "d0110db319fc97ef0a599b3d0cf2b36334a2a060f648a7320583195d27c46a36",
"view_tag": "5f"
}
}
}
],
"extra": [ 1, 176, 18, 69, 233, 37, 10, 116, 174, 71, 48, 60, 164, 144, 168, 186, 183, 95, 11, 140, 126, 53, 234, 248, 35, 162, 135, 236, 231, 213, 42, 136, 44, 2, 9, 0, 0, 0, 2, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}