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: 270bbb99d104861572a7dbe113109a78c672b61505b978898fe3a9147d8ae4c8
Tx prefix hash: e082350e26d2cb87c2fc0543e38ef8c46069543b4c29a59d493a1ae30903b8d7
Tx public key: aacc007a71f1b862473c5457f8e8df22f79c7a7ba97085b5b55f6f306a09d938
| Timestamp: 1779640204 | Timestamp [UTC]: 2026-05-24 16:30:04 | Age [y:d:h:m:s]: 00:015:08:16:43 |
| Block: 1284 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6602 | RingCT/type: yes/0 |
| Extra: 01aacc007a71f1b862473c5457f8e8df22f79c7a7ba97085b5b55f6f306a09d938020900000001ba6d17be00 | ||
1 output(s) for total of 35.098376598335 HMNY
| stealth address | amount | amount idx | tag |
| 00: 501687ec6cebfb755be3a843003dd233940f850110dd11a3e2327efa30d3481d | 35.098376598335 | 1432 of 0 | <9c> |
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": 1344,
"vin": [ {
"gen": {
"height": 1284
}
}
],
"vout": [ {
"amount": 35098376598335,
"target": {
"tagged_key": {
"key": "501687ec6cebfb755be3a843003dd233940f850110dd11a3e2327efa30d3481d",
"view_tag": "9c"
}
}
}
],
"extra": [ 1, 170, 204, 0, 122, 113, 241, 184, 98, 71, 60, 84, 87, 248, 232, 223, 34, 247, 156, 122, 123, 169, 112, 133, 181, 181, 95, 111, 48, 106, 9, 217, 56, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}