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: 2f2615311cbaa2671440f2becf77082ac495ccfea0511f957fe41b94da0d8665
Tx prefix hash: 1707f821d3297bcf9200e173e54e1860e9a804fe9f78ab96ab21f9d42a7b50f7
Tx public key: 6be8cde13dc6d03ecbaf454068924f8f21d75117d6b2cb345942478807049334
| Timestamp: 1779732735 | Timestamp [UTC]: 2026-05-25 18:12:15 | Age [y:d:h:m:s]: 00:014:06:34:32 |
| Block: 1894 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5992 | RingCT/type: yes/0 |
| Extra: 016be8cde13dc6d03ecbaf454068924f8f21d75117d6b2cb345942478807049334020900000001ba6d17be00 | ||
1 output(s) for total of 35.057563953642 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5553b8d7b6bb84c0355c77bbe02f7ea5c275c0643d1914424846b0685288cd5f | 35.057563953642 | 2117 of 0 | <1c> |
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": 1954,
"vin": [ {
"gen": {
"height": 1894
}
}
],
"vout": [ {
"amount": 35057563953642,
"target": {
"tagged_key": {
"key": "5553b8d7b6bb84c0355c77bbe02f7ea5c275c0643d1914424846b0685288cd5f",
"view_tag": "1c"
}
}
}
],
"extra": [ 1, 107, 232, 205, 225, 61, 198, 208, 62, 203, 175, 69, 64, 104, 146, 79, 143, 33, 215, 81, 23, 214, 178, 203, 52, 89, 66, 71, 136, 7, 4, 147, 52, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}