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: 858e4d15e943a4a485da7e00c8aca87eed6383dcead4abb5d1968ab3b428baa4
Tx prefix hash: 78a5cb83ea77563f74ffba15597e02d7806738a1b576255ec26f3c68b7755374
Tx public key: c9d2bcbf31504d90259f77e8898ac59695152ad93cf227aeb26dcc7a358d510c
| Timestamp: 1781002306 | Timestamp [UTC]: 2026-06-09 10:51:46 | Age [y:d:h:m:s]: 00:007:21:13:35 |
| Block: 8473 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 272 | RingCT/type: yes/0 |
| Extra: 01c9d2bcbf31504d90259f77e8898ac59695152ad93cf227aeb26dcc7a358d510c020900000001e49593ff00 | ||
1 output(s) for total of 34.620394202752 HMNY
| stealth address | amount | amount idx | tag |
| 00: 30d68373a66093efa6bae17874477d9dd2e33b16376fa78b932ee26426545630 | 34.620394202752 | 10469 of 0 | <43> |
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": 8533,
"vin": [ {
"gen": {
"height": 8473
}
}
],
"vout": [ {
"amount": 34620394202752,
"target": {
"tagged_key": {
"key": "30d68373a66093efa6bae17874477d9dd2e33b16376fa78b932ee26426545630",
"view_tag": "43"
}
}
}
],
"extra": [ 1, 201, 210, 188, 191, 49, 80, 77, 144, 37, 159, 119, 232, 137, 138, 197, 150, 149, 21, 42, 217, 60, 242, 39, 174, 178, 109, 204, 122, 53, 141, 81, 12, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}