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: 1b394bc481912b690b276030645c266df603146c9c4a25422c44de0e4e4b7bec
Tx prefix hash: d8ee23440044f90f567127769790c0850e75a9b16c8411c0e4eb5c853a61c6be
Tx public key: 4447827cb9f90cac8783744354b27eae0ce5f06c66cb7bec685d87c8fe9a1b36
| Timestamp: 1780690739 | Timestamp [UTC]: 2026-06-05 20:18:59 | Age [y:d:h:m:s]: 00:003:06:21:37 |
| Block: 5681 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2217 | RingCT/type: yes/0 |
| Extra: 014447827cb9f90cac8783744354b27eae0ce5f06c66cb7bec685d87c8fe9a1b36020900000001e49593ff00 | ||
1 output(s) for total of 34.805250739093 HMNY
| stealth address | amount | amount idx | tag |
| 00: 30c489332c893659f1dbc7ac99357d923c6380bb50182722a5c7427c36ce8577 | 34.805250739093 | 7130 of 0 | <58> |
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": 5741,
"vin": [ {
"gen": {
"height": 5681
}
}
],
"vout": [ {
"amount": 34805250739093,
"target": {
"tagged_key": {
"key": "30c489332c893659f1dbc7ac99357d923c6380bb50182722a5c7427c36ce8577",
"view_tag": "58"
}
}
}
],
"extra": [ 1, 68, 71, 130, 124, 185, 249, 12, 172, 135, 131, 116, 67, 84, 178, 126, 174, 12, 229, 240, 108, 102, 203, 123, 236, 104, 93, 135, 200, 254, 154, 27, 54, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}