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: a2b5c1fe75f89e5b332124cab807ff23a75a035f3a6bdd3481f86c0bcb25e0a5
Tx prefix hash: eee3a6f2669f8700be0283800fe807df67a3e0c05e700045fb71d1b4980af368
Tx public key: 4ec0832a2fb95d6b083cc637d0c1ae6931e12f89e507400505ac6156b1ff40e9
| Timestamp: 1779932253 | Timestamp [UTC]: 2026-05-28 01:37:33 | Age [y:d:h:m:s]: 00:011:23:09:14 |
| Block: 3408 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4478 | RingCT/type: yes/0 |
| Extra: 014ec0832a2fb95d6b083cc637d0c1ae6931e12f89e507400505ac6156b1ff40e902090000000126697be300 | ||
1 output(s) for total of 34.956473255625 HMNY
| stealth address | amount | amount idx | tag |
| 00: f22382b142a11321c9a69627b56da4314e31a5fa0ab11c0a4938e10f5f47fbaf | 34.956473255625 | 4123 of 0 | <67> |
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": 3468,
"vin": [ {
"gen": {
"height": 3408
}
}
],
"vout": [ {
"amount": 34956473255625,
"target": {
"tagged_key": {
"key": "f22382b142a11321c9a69627b56da4314e31a5fa0ab11c0a4938e10f5f47fbaf",
"view_tag": "67"
}
}
}
],
"extra": [ 1, 78, 192, 131, 42, 47, 185, 93, 107, 8, 60, 198, 55, 208, 193, 174, 105, 49, 225, 47, 137, 229, 7, 64, 5, 5, 172, 97, 86, 177, 255, 64, 233, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}