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: 020cc31b7c9482734d1222078b11f87b6e4eb28678fb62e7a222c49fe936324c
Tx prefix hash: 8f470ffe98a88aedd726334f04ef0bbcf5a88de5828fdac39bf61bded4d6afb7
Tx public key: 47f96679b98a1330d550feaaf4f3d95a4081804a5c544b1b1818d2cf68acd03a
| Timestamp: 1780761937 | Timestamp [UTC]: 2026-06-06 16:05:37 | Age [y:d:h:m:s]: 00:002:10:44:11 |
| Block: 6580 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1320 | RingCT/type: yes/0 |
| Extra: 0147f96679b98a1330d550feaaf4f3d95a4081804a5c544b1b1818d2cf68acd03a020900000001e49593ff00 | ||
1 output(s) for total of 34.745621033632 HMNY
| stealth address | amount | amount idx | tag |
| 00: 97f6fd810a23eb50b8b7a50c4338f6ae633f661fc7d257b99d757aa082ba55ee | 34.745621033632 | 8104 of 0 | <43> |
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": 6640,
"vin": [ {
"gen": {
"height": 6580
}
}
],
"vout": [ {
"amount": 34745621033632,
"target": {
"tagged_key": {
"key": "97f6fd810a23eb50b8b7a50c4338f6ae633f661fc7d257b99d757aa082ba55ee",
"view_tag": "43"
}
}
}
],
"extra": [ 1, 71, 249, 102, 121, 185, 138, 19, 48, 213, 80, 254, 170, 244, 243, 217, 90, 64, 129, 128, 74, 92, 84, 75, 27, 24, 24, 210, 207, 104, 172, 208, 58, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}