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: 1e99f38b1a955e08a059624553cbf9e9e2003b036a719c24c14ed91bcf3dd67c
Tx prefix hash: abd0eea2fe21b06ad9b376c8539b62aa16683ee66a53b1f4c8e38d26dd2cf728
Tx public key: 33869f185ab6dd6b615d6f3e4cfecdc0de8306c4eaac519471d4ba3f70a948d9
| Timestamp: 1779879157 | Timestamp [UTC]: 2026-05-27 10:52:37 | Age [y:d:h:m:s]: 00:012:14:43:20 |
| Block: 2924 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4962 | RingCT/type: yes/0 |
| Extra: 0133869f185ab6dd6b615d6f3e4cfecdc0de8306c4eaac519471d4ba3f70a948d902090000000126697be300 | ||
1 output(s) for total of 34.988758490120 HMNY
| stealth address | amount | amount idx | tag |
| 00: e3cb4bdc32b656f770d2146ab89f31ae083a77fdeb7e67d37781e92110ecd6f7 | 34.988758490120 | 3466 of 0 | <c3> |
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": 2984,
"vin": [ {
"gen": {
"height": 2924
}
}
],
"vout": [ {
"amount": 34988758490120,
"target": {
"tagged_key": {
"key": "e3cb4bdc32b656f770d2146ab89f31ae083a77fdeb7e67d37781e92110ecd6f7",
"view_tag": "c3"
}
}
}
],
"extra": [ 1, 51, 134, 159, 24, 90, 182, 221, 107, 97, 93, 111, 62, 76, 254, 205, 192, 222, 131, 6, 196, 234, 172, 81, 148, 113, 212, 186, 63, 112, 169, 72, 217, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}