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: a2bc5cfbb5c014989915db3795ff0cbe2b94f30cab439a9cda4d97f47696e660
Tx prefix hash: b18942978cbf20adf4d087b01e235f9c46eea5b99f5f80c3078c15edea62c54e
Tx public key: 33a2f976504a07c5d86c140973cacdd49bdd80536aaa9b29da5b23484f0551c5
| Timestamp: 1779967528 | Timestamp [UTC]: 2026-05-28 11:25:28 | Age [y:d:h:m:s]: 00:012:05:43:35 |
| Block: 3820 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4915 | RingCT/type: yes/0 |
| Extra: 0133a2f976504a07c5d86c140973cacdd49bdd80536aaa9b29da5b23484f0551c502090000000526697be300 | ||
1 output(s) for total of 34.929014257105 HMNY
| stealth address | amount | amount idx | tag |
| 00: 35d0ae6d195b045e6652089f2d136908aa87c7da319ec1b716f89a8b0b842ebe | 34.929014257105 | 4652 of 0 | <50> |
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": 3880,
"vin": [ {
"gen": {
"height": 3820
}
}
],
"vout": [ {
"amount": 34929014257105,
"target": {
"tagged_key": {
"key": "35d0ae6d195b045e6652089f2d136908aa87c7da319ec1b716f89a8b0b842ebe",
"view_tag": "50"
}
}
}
],
"extra": [ 1, 51, 162, 249, 118, 80, 74, 7, 197, 216, 108, 20, 9, 115, 202, 205, 212, 155, 221, 128, 83, 106, 170, 155, 41, 218, 91, 35, 72, 79, 5, 81, 197, 2, 9, 0, 0, 0, 5, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}