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: be942bf34162cf49296cb8884de43c3658d6bbebcd62b11369220141c2f120a3
Tx prefix hash: 060fa1934a4b9f9cee807c9c75fbeb46d55cad080daa81ccbbb19ffdebd352a2
Tx public key: 65e23f58297028a5438c2b080244a2e0ff29efc1ab9b2926bd1ba32585273b3e
| Timestamp: 1779878844 | Timestamp [UTC]: 2026-05-27 10:47:24 | Age [y:d:h:m:s]: 00:012:13:59:23 |
| Block: 2918 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4968 | RingCT/type: yes/0 |
| Extra: 0165e23f58297028a5438c2b080244a2e0ff29efc1ab9b2926bd1ba32585273b3e02090000000226697be300 | ||
1 output(s) for total of 34.989158907358 HMNY
| stealth address | amount | amount idx | tag |
| 00: 87c092932f6e92b05255838c2f2ab87e066fa7bebe700990e3c7ed5f80d6852e | 34.989158907358 | 3458 of 0 | <71> |
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": 2978,
"vin": [ {
"gen": {
"height": 2918
}
}
],
"vout": [ {
"amount": 34989158907358,
"target": {
"tagged_key": {
"key": "87c092932f6e92b05255838c2f2ab87e066fa7bebe700990e3c7ed5f80d6852e",
"view_tag": "71"
}
}
}
],
"extra": [ 1, 101, 226, 63, 88, 41, 112, 40, 165, 67, 140, 43, 8, 2, 68, 162, 224, 255, 41, 239, 193, 171, 155, 41, 38, 189, 27, 163, 37, 133, 39, 59, 62, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}