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: e0fd827fff2c60cc5ba5ba5b686c17f6027706155a952cd23a9dbb8cb6d20959
Tx prefix hash: 40ba512eabee1cc45dae6f9b932d794ccf653ce853d7ee81e5f3c50fa584def0
Tx public key: 8848531c7cc7c5e2e053d94774d34b3579af8fa0b5c6d5f7f355be19bb3c1ea0
| Timestamp: 1780801250 | Timestamp [UTC]: 2026-06-07 03:00:50 | Age [y:d:h:m:s]: 00:001:22:35:07 |
| Block: 6841 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1045 | RingCT/type: yes/0 |
| Extra: 018848531c7cc7c5e2e053d94774d34b3579af8fa0b5c6d5f7f355be19bb3c1ea0020900000002e49593ff00 | ||
1 output(s) for total of 34.728328326474 HMNY
| stealth address | amount | amount idx | tag |
| 00: f6aa6628e7b9a4c40688773a23b3397eb3ec4cbaf5c637fdf27ec03c33118f11 | 34.728328326474 | 8447 of 0 | <a2> |
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": 6901,
"vin": [ {
"gen": {
"height": 6841
}
}
],
"vout": [ {
"amount": 34728328326474,
"target": {
"tagged_key": {
"key": "f6aa6628e7b9a4c40688773a23b3397eb3ec4cbaf5c637fdf27ec03c33118f11",
"view_tag": "a2"
}
}
}
],
"extra": [ 1, 136, 72, 83, 28, 124, 199, 197, 226, 224, 83, 217, 71, 116, 211, 75, 53, 121, 175, 143, 160, 181, 198, 213, 247, 243, 85, 190, 25, 187, 60, 30, 160, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}