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: 8e0edcf27ec6efd9c37e4f70df089ea75a43399c528e187cbecb6810a2924ad5
Tx prefix hash: fd32b466f11b0cf4162fcc7974f8269e00cb330d8b9da6fcd63de9057a1c5703
Tx public key: 2c8edfef3751c0a26642cd786333a4a490b2b00b3f304af04f233c772584141f
| Timestamp: 1779643244 | Timestamp [UTC]: 2026-05-24 17:20:44 | Age [y:d:h:m:s]: 00:023:15:54:22 |
| Block: 1404 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7341 | RingCT/type: yes/0 |
| Extra: 012c8edfef3751c0a26642cd786333a4a490b2b00b3f304af04f233c772584141f020900000002ba6d17be00 | ||
1 output(s) for total of 35.090344129079 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4c2ab6eeedddbd0440367035343e658a3357ba14843aa9ce80a20f7e008774d1 | 35.090344129079 | 1556 of 0 | <10> |
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": 1464,
"vin": [ {
"gen": {
"height": 1404
}
}
],
"vout": [ {
"amount": 35090344129079,
"target": {
"tagged_key": {
"key": "4c2ab6eeedddbd0440367035343e658a3357ba14843aa9ce80a20f7e008774d1",
"view_tag": "10"
}
}
}
],
"extra": [ 1, 44, 142, 223, 239, 55, 81, 192, 162, 102, 66, 205, 120, 99, 51, 164, 164, 144, 178, 176, 11, 63, 48, 74, 240, 79, 35, 60, 119, 37, 132, 20, 31, 2, 9, 0, 0, 0, 2, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}