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: 1df30334cee1af79bfb922ef931b8223f78bb6597e90091a1824103e3f11c961
Tx prefix hash: e60e2aa0b9a0ce2ed8af4bb4e04e27a49ed6ab317990fb04f7aa6c6c2e06b79c
Tx public key: 138e7d4a3f40e72d3ebd4e97b2726ea2c328ab2f4b8f708db049d69aec870919
| Timestamp: 1780693099 | Timestamp [UTC]: 2026-06-05 20:58:19 | Age [y:d:h:m:s]: 00:003:02:20:34 |
| Block: 5844 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2042 | RingCT/type: yes/0 |
| Extra: 01138e7d4a3f40e72d3ebd4e97b2726ea2c328ab2f4b8f708db049d69aec870919020900000001e49593ff00 | ||
1 output(s) for total of 34.794431533868 HMNY
| stealth address | amount | amount idx | tag |
| 00: c8526f0285b6bf456fb40adc212bfe74d801dd55be2a9e99d08152012cdf96e4 | 34.794431533868 | 7301 of 0 | <74> |
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": 5904,
"vin": [ {
"gen": {
"height": 5844
}
}
],
"vout": [ {
"amount": 34794431533868,
"target": {
"tagged_key": {
"key": "c8526f0285b6bf456fb40adc212bfe74d801dd55be2a9e99d08152012cdf96e4",
"view_tag": "74"
}
}
}
],
"extra": [ 1, 19, 142, 125, 74, 63, 64, 231, 45, 62, 189, 78, 151, 178, 114, 110, 162, 195, 40, 171, 47, 75, 143, 112, 141, 176, 73, 214, 154, 236, 135, 9, 25, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}