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: 5ce79e0c64e16df1e7cf22f11e09dfc41762f05c572a658b537a42dd6d649881
Tx prefix hash: a4aae7ba573a68bad96ea58b346c7da532d24bf00152e73bb19710e387c3e199
Tx public key: b27cec07eb67499335abd9df9a88f9e54577e235966a50c292274080d87ec157
| Timestamp: 1779957485 | Timestamp [UTC]: 2026-05-28 08:38:05 | Age [y:d:h:m:s]: 00:011:14:40:48 |
| Block: 3715 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4171 | RingCT/type: yes/0 |
| Extra: 01b27cec07eb67499335abd9df9a88f9e54577e235966a50c292274080d87ec15702090000000426697be300 | ||
1 output(s) for total of 34.936010254100 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3b9a229d7bd665dd02d44393b1abd59a2cf83a8a2f5c4e2417ef0f4143e96a5e | 34.936010254100 | 4495 of 0 | <df> |
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": 3775,
"vin": [ {
"gen": {
"height": 3715
}
}
],
"vout": [ {
"amount": 34936010254100,
"target": {
"tagged_key": {
"key": "3b9a229d7bd665dd02d44393b1abd59a2cf83a8a2f5c4e2417ef0f4143e96a5e",
"view_tag": "df"
}
}
}
],
"extra": [ 1, 178, 124, 236, 7, 235, 103, 73, 147, 53, 171, 217, 223, 154, 136, 249, 229, 69, 119, 226, 53, 150, 106, 80, 194, 146, 39, 64, 128, 216, 126, 193, 87, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}