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: 6fe01844bff910afd3e68451eb0c8d43fe70a170847acdaf9d63a3e9d4bcefbc
Tx prefix hash: dfef51b73994e69f1bf36913620a27f26055b425cbc6d0886c976c47a188ec9d
Tx public key: 026d5c26225b5a763e8e993395ac32bde2fe2cd78790f1be7fcdf1132e9e89cc
| Timestamp: 1779434829 | Timestamp [UTC]: 2026-05-22 07:27:09 | Age [y:d:h:m:s]: 00:022:03:35:07 |
| Block: 105 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0918 kB |
| Tx version: 2 | No of confirmations: 8640 | RingCT/type: yes/0 |
| Extra: 01026d5c26225b5a763e8e993395ac32bde2fe2cd78790f1be7fcdf1132e9e89cc020900000001a662ed0300 | ||
1 output(s) for total of 35.177393452613 HMNY
| stealth address | amount | amount idx | tag |
| 00: c2a54b9860750e092977832414667ee01af202a42491b724391dbc9e83410c4b | 35.177393452613 | 101 of 0 | <38> |
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": 165,
"vin": [ {
"gen": {
"height": 105
}
}
],
"vout": [ {
"amount": 35177393452613,
"target": {
"tagged_key": {
"key": "c2a54b9860750e092977832414667ee01af202a42491b724391dbc9e83410c4b",
"view_tag": "38"
}
}
}
],
"extra": [ 1, 2, 109, 92, 38, 34, 91, 90, 118, 62, 142, 153, 51, 149, 172, 50, 189, 226, 254, 44, 215, 135, 144, 241, 190, 127, 205, 241, 19, 46, 158, 137, 204, 2, 9, 0, 0, 0, 1, 166, 98, 237, 3, 0
],
"rct_signatures": {
"type": 0
}
}