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: 94c90d4a5befed401519fcb86ab2d099f07b2752b91fdfce6cd7fa75b7905d07
Tx prefix hash: 0d0743b7541e2d7b3c53b9603f572ff0d81024e2c917ef228db22eba4ee80c44
Tx public key: 828923ac01e0a58c5c5168aba467249ee3b55d00c7b2d5606e38139c60f1ca40
| Timestamp: 1779916012 | Timestamp [UTC]: 2026-05-27 21:06:52 | Age [y:d:h:m:s]: 00:012:05:33:44 |
| Block: 3301 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4595 | RingCT/type: yes/0 |
| Extra: 01828923ac01e0a58c5c5168aba467249ee3b55d00c7b2d5606e38139c60f1ca4002090000000826697be300 | ||
1 output(s) for total of 34.963608127887 HMNY
| stealth address | amount | amount idx | tag |
| 00: aabd75a63cc73f5fd077a3b0a9a3b7938b73a809a55f96be1c6e4700e9c11b44 | 34.963608127887 | 3965 of 0 | <a5> |
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": 3361,
"vin": [ {
"gen": {
"height": 3301
}
}
],
"vout": [ {
"amount": 34963608127887,
"target": {
"tagged_key": {
"key": "aabd75a63cc73f5fd077a3b0a9a3b7938b73a809a55f96be1c6e4700e9c11b44",
"view_tag": "a5"
}
}
}
],
"extra": [ 1, 130, 137, 35, 172, 1, 224, 165, 140, 92, 81, 104, 171, 164, 103, 36, 158, 227, 181, 93, 0, 199, 178, 213, 96, 110, 56, 19, 156, 96, 241, 202, 64, 2, 9, 0, 0, 0, 8, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}