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: 08adb2e04eb7fc7d599f307f6d8e589ee57a15a0a19f4047142e6542dc3658ee
Tx prefix hash: 505096ccfe0bb8d2870b8e17581734bbb928615602f080ffb3f18fd0e01adc68
Tx public key: 4cd3e4a7561a72b48459a1799442be480b0ee655d74aa189a58be2e4b1a98c45
| Timestamp: 1779785062 | Timestamp [UTC]: 2026-05-26 08:44:22 | Age [y:d:h:m:s]: 00:013:16:02:25 |
| Block: 2154 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5732 | RingCT/type: yes/0 |
| Extra: 014cd3e4a7561a72b48459a1799442be480b0ee655d74aa189a58be2e4b1a98c4502090000000326697be300 | ||
1 output(s) for total of 35.040182828029 HMNY
| stealth address | amount | amount idx | tag |
| 00: e65912e823fd4163f4eca45cc287b64a8c3257757acdfccf75a14328e35270f8 | 35.040182828029 | 2486 of 0 | <aa> |
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": 2214,
"vin": [ {
"gen": {
"height": 2154
}
}
],
"vout": [ {
"amount": 35040182828029,
"target": {
"tagged_key": {
"key": "e65912e823fd4163f4eca45cc287b64a8c3257757acdfccf75a14328e35270f8",
"view_tag": "aa"
}
}
}
],
"extra": [ 1, 76, 211, 228, 167, 86, 26, 114, 180, 132, 89, 161, 121, 148, 66, 190, 72, 11, 14, 230, 85, 215, 74, 161, 137, 165, 139, 226, 228, 177, 169, 140, 69, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}