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: 3ccec20d016c200e2698d20c76e815e74c12eeb3ba6ab524f51b810b0fbf56e5
Tx prefix hash: 539e93bf0a98b98c0c853de303a0dc7ba47ab374d4c9bd5ce1ea779da3fa618c
Tx public key: 5de5f9a9c17caf7a6bbac14b2f4d601313f9c148f8ebd189124e9429dfa084a9
| Timestamp: 1779849733 | Timestamp [UTC]: 2026-05-27 02:42:13 | Age [y:d:h:m:s]: 00:013:00:07:35 |
| Block: 2513 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5407 | RingCT/type: yes/0 |
| Extra: 015de5f9a9c17caf7a6bbac14b2f4d601313f9c148f8ebd189124e9429dfa084a902090000000126697be300 | ||
1 output(s) for total of 35.016197667583 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7f9b207e26b83f05b8943167a2b36f7027614ee4fb939589cb3b817833f78b7e | 35.016197667583 | 2957 of 0 | <ca> |
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": 2573,
"vin": [ {
"gen": {
"height": 2513
}
}
],
"vout": [ {
"amount": 35016197667583,
"target": {
"tagged_key": {
"key": "7f9b207e26b83f05b8943167a2b36f7027614ee4fb939589cb3b817833f78b7e",
"view_tag": "ca"
}
}
}
],
"extra": [ 1, 93, 229, 249, 169, 193, 124, 175, 122, 107, 186, 193, 75, 47, 77, 96, 19, 19, 249, 193, 72, 248, 235, 209, 137, 18, 78, 148, 41, 223, 160, 132, 169, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}