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: 58c9a7bff1bc95d2a0fe4071b1f7fa48804703e96a4257dc10de3483851bbad8
Tx prefix hash: dbe1ea53ac719f69d6cbccba37ef6db427ee49d48e3d5fe898341d48c1418719
Tx public key: e0f7e31d145efba4242ff4d304485f3a6d8b2e78d91b90e9b3a031ceac96c862
| Timestamp: 1779960724 | Timestamp [UTC]: 2026-05-28 09:32:04 | Age [y:d:h:m:s]: 00:011:17:08:32 |
| Block: 3757 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4140 | RingCT/type: yes/0 |
| Extra: 01e0f7e31d145efba4242ff4d304485f3a6d8b2e78d91b90e9b3a031ceac96c86202090000000426697be300 | ||
1 output(s) for total of 34.933211687169 HMNY
| stealth address | amount | amount idx | tag |
| 00: 10db59e4362ad7642a21e0a6406f95812e5b32923ee3ca5f84f8b58a151d53dc | 34.933211687169 | 4555 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": 3817,
"vin": [ {
"gen": {
"height": 3757
}
}
],
"vout": [ {
"amount": 34933211687169,
"target": {
"tagged_key": {
"key": "10db59e4362ad7642a21e0a6406f95812e5b32923ee3ca5f84f8b58a151d53dc",
"view_tag": "68"
}
}
}
],
"extra": [ 1, 224, 247, 227, 29, 20, 94, 251, 164, 36, 47, 244, 211, 4, 72, 95, 58, 109, 139, 46, 120, 217, 27, 144, 233, 179, 160, 49, 206, 172, 150, 200, 98, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}