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: 20e192b99837e835620b1f1d044337cda2b89ea30c37c847538d19854a60a287
Tx prefix hash: 801920180a088c605208131b79d14b08c8a0220e6b63546e975e3d8659434961
Tx public key: f3ac00b90708eb044bcfe03e0be4d5445d29a9d89893b1648be846010d4da13c
| Timestamp: 1779715371 | Timestamp [UTC]: 2026-05-25 13:22:51 | Age [y:d:h:m:s]: 00:014:11:23:56 |
| Block: 1632 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6254 | RingCT/type: yes/0 |
| Extra: 01f3ac00b90708eb044bcfe03e0be4d5445d29a9d89893b1648be846010d4da13c020900000003ba6d17be00 | ||
1 output(s) for total of 35.075087501599 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8c7a5b3a46db778532dcd7f408725ae719355f96f92c2d5163ffe3a65d0fc13b | 35.075087501599 | 1792 of 0 | <a0> |
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": 1692,
"vin": [ {
"gen": {
"height": 1632
}
}
],
"vout": [ {
"amount": 35075087501599,
"target": {
"tagged_key": {
"key": "8c7a5b3a46db778532dcd7f408725ae719355f96f92c2d5163ffe3a65d0fc13b",
"view_tag": "a0"
}
}
}
],
"extra": [ 1, 243, 172, 0, 185, 7, 8, 235, 4, 75, 207, 224, 62, 11, 228, 213, 68, 93, 41, 169, 216, 152, 147, 177, 100, 139, 232, 70, 1, 13, 77, 161, 60, 2, 9, 0, 0, 0, 3, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}