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: 1a6259511d5058481a9fe2d43833d6596f33f1460c1236b67477e28af7941df8
Tx prefix hash: 28fd75ada63f598679f9d7727a8254223a8947690f634e8caff5a68eb5489bb2
Tx public key: 20dbbe7c345063734f099a429d5d74fe1c184d73972f60bb61580751eb6d842e
| Timestamp: 1780854761 | Timestamp [UTC]: 2026-06-07 17:52:41 | Age [y:d:h:m:s]: 00:001:08:57:07 |
| Block: 7561 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 338 | RingCT/type: yes/0 |
| Extra: 0120dbbe7c345063734f099a429d5d74fe1c184d73972f60bb61580751eb6d842e020900000001e49593ff00 | ||
1 output(s) for total of 34.680668912357 HMNY
| stealth address | amount | amount idx | tag |
| 00: e295a5476cce613c7b1f748d39b7b3fb61a7cec854d64d3fce57a8ae8d7d8cd9 | 34.680668912357 | 9337 of 0 | <85> |
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": 7621,
"vin": [ {
"gen": {
"height": 7561
}
}
],
"vout": [ {
"amount": 34680668912357,
"target": {
"tagged_key": {
"key": "e295a5476cce613c7b1f748d39b7b3fb61a7cec854d64d3fce57a8ae8d7d8cd9",
"view_tag": "85"
}
}
}
],
"extra": [ 1, 32, 219, 190, 124, 52, 80, 99, 115, 79, 9, 154, 66, 157, 93, 116, 254, 28, 24, 77, 115, 151, 47, 96, 187, 97, 88, 7, 81, 235, 109, 132, 46, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}