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: 34f2196fd13228998f1701385aa76d3409c10f6260cb3a22c9dcf2f0cc99f2b8
Tx prefix hash: c6f76144c9ac999f1e6e0e3a2ddf77c6bd7793de34d01049ef75e4d60d19a06f
Tx public key: 57fe862c71444a70797ed00c8a04eb1a524b88050750b24c5db2b78a3edd88fe
| Timestamp: 1779875666 | Timestamp [UTC]: 2026-05-27 09:54:26 | Age [y:d:h:m:s]: 00:012:16:55:22 |
| Block: 2883 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5037 | RingCT/type: yes/0 |
| Extra: 0157fe862c71444a70797ed00c8a04eb1a524b88050750b24c5db2b78a3edd88fe02090000000226697be300 | ||
1 output(s) for total of 34.991494765906 HMNY
| stealth address | amount | amount idx | tag |
| 00: b515eb2d4210fd03f15cf3b92d93a39478895884a998cdc56ab11ec85211a387 | 34.991494765906 | 3413 of 0 | <1e> |
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": 2943,
"vin": [ {
"gen": {
"height": 2883
}
}
],
"vout": [ {
"amount": 34991494765906,
"target": {
"tagged_key": {
"key": "b515eb2d4210fd03f15cf3b92d93a39478895884a998cdc56ab11ec85211a387",
"view_tag": "1e"
}
}
}
],
"extra": [ 1, 87, 254, 134, 44, 113, 68, 74, 112, 121, 126, 208, 12, 138, 4, 235, 26, 82, 75, 136, 5, 7, 80, 178, 76, 93, 178, 183, 138, 62, 221, 136, 254, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}