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: 50f7b2cc74a59f3889ab54a756e5d02f7526069b031b77552c3ef3ba9e698a93
Tx prefix hash: df233176383fcb231fd5b8b2b5c392526b2b5e873e97141598f14b486510828f
Tx public key: 09fb795e9438cdc0ffdfa6e774ec5dc20a3afd149dc1d2d25cf05e6db3c077ec
| Timestamp: 1779854786 | Timestamp [UTC]: 2026-05-27 04:06:26 | Age [y:d:h:m:s]: 00:012:22:43:22 |
| Block: 2601 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5298 | RingCT/type: yes/0 |
| Extra: 0109fb795e9438cdc0ffdfa6e774ec5dc20a3afd149dc1d2d25cf05e6db3c077ec02090000000126697be300 | ||
1 output(s) for total of 35.010320802684 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3fb7ced6c591dcfa1cb827b4ed7f58662aa61ca51a7ca20ad35fb8c5c8909fff | 35.010320802684 | 3061 of 0 | <25> |
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": 2661,
"vin": [ {
"gen": {
"height": 2601
}
}
],
"vout": [ {
"amount": 35010320802684,
"target": {
"tagged_key": {
"key": "3fb7ced6c591dcfa1cb827b4ed7f58662aa61ca51a7ca20ad35fb8c5c8909fff",
"view_tag": "25"
}
}
}
],
"extra": [ 1, 9, 251, 121, 94, 148, 56, 205, 192, 255, 223, 166, 231, 116, 236, 93, 194, 10, 58, 253, 20, 157, 193, 210, 210, 92, 240, 94, 109, 179, 192, 119, 236, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}