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: 0686cddc38b99e6dcb5848760efa8e0f79ede76769977976629ec1cf6d2ebd8d
Tx prefix hash: d96ca2e34cb6e850499a4322114fb3d90df1dd2b2f86ae00be9b208df40ecdd4
Tx public key: 440f4c65ad45e9a2bc33bc1c8b24605acd5ee85c966fdd2f6fb17eaa1a8c60e2
| Timestamp: 1780693853 | Timestamp [UTC]: 2026-06-05 21:10:53 | Age [y:d:h:m:s]: 00:007:13:51:23 |
| Block: 5904 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2841 | RingCT/type: yes/0 |
| Extra: 01440f4c65ad45e9a2bc33bc1c8b24605acd5ee85c966fdd2f6fb17eaa1a8c60e2020900000001e49593ff00 | ||
1 output(s) for total of 34.790449851224 HMNY
| stealth address | amount | amount idx | tag |
| 00: f7ed877af6a035927d355395309abd6ead94644e4478bcb3a80de243a8b852f9 | 34.790449851224 | 7365 of 0 | <68> |
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": 5964,
"vin": [ {
"gen": {
"height": 5904
}
}
],
"vout": [ {
"amount": 34790449851224,
"target": {
"tagged_key": {
"key": "f7ed877af6a035927d355395309abd6ead94644e4478bcb3a80de243a8b852f9",
"view_tag": "68"
}
}
}
],
"extra": [ 1, 68, 15, 76, 101, 173, 69, 233, 162, 188, 51, 188, 28, 139, 36, 96, 90, 205, 94, 232, 92, 150, 111, 221, 47, 111, 177, 126, 170, 26, 140, 96, 226, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}