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: 9c254bbd88954ff8b9f58d3e306ee77cae9858a1595e076e5c7fde2f18c846ab
Tx prefix hash: 76fb8fe05301d1bbdf0ee28fd4bd1715f4e47c774b521e02736283639f45c8f2
Tx public key: 86c509275615cc651498f468fa107ac8e5c2f1ee51b66244defeabb2d6104fde
| Timestamp: 1779806083 | Timestamp [UTC]: 2026-05-26 14:34:43 | Age [y:d:h:m:s]: 00:013:11:01:14 |
| Block: 2349 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5537 | RingCT/type: yes/0 |
| Extra: 0186c509275615cc651498f468fa107ac8e5c2f1ee51b66244defeabb2d6104fde02090000000326697be300 | ||
1 output(s) for total of 35.027152639193 HMNY
| stealth address | amount | amount idx | tag |
| 00: 421e074f88e6f1bc177997f6c86dbf1abc5e8db03c5652dbd866bbdf6ede4c95 | 35.027152639193 | 2751 of 0 | <6e> |
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": 2409,
"vin": [ {
"gen": {
"height": 2349
}
}
],
"vout": [ {
"amount": 35027152639193,
"target": {
"tagged_key": {
"key": "421e074f88e6f1bc177997f6c86dbf1abc5e8db03c5652dbd866bbdf6ede4c95",
"view_tag": "6e"
}
}
}
],
"extra": [ 1, 134, 197, 9, 39, 86, 21, 204, 101, 20, 152, 244, 104, 250, 16, 122, 200, 229, 194, 241, 238, 81, 182, 98, 68, 222, 254, 171, 178, 214, 16, 79, 222, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}