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: f75fcacec325e6af807cad7a00fdb8750d938464900819fd7e2d0e147d90efe2
Tx prefix hash: f1e2bb3cf6871037be7d9f170abfcd69818cd4eeb577123199af4401faf9f8b5
Tx public key: d33e4a789d07d6f36f962884d9ccf1c13e2cc1f07bb3af093932710403c39108
| Timestamp: 1780690916 | Timestamp [UTC]: 2026-06-05 20:21:56 | Age [y:d:h:m:s]: 00:003:02:56:57 |
| Block: 5697 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2189 | RingCT/type: yes/0 |
| Extra: 01d33e4a789d07d6f36f962884d9ccf1c13e2cc1f07bb3af093932710403c39108020900000001e49593ff00 | ||
1 output(s) for total of 34.804188582329 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5984a8e8ecabd0944f3e850631f633c2e5108bf9df8058932193a095146840c6 | 34.804188582329 | 7148 of 0 | <81> |
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": 5757,
"vin": [ {
"gen": {
"height": 5697
}
}
],
"vout": [ {
"amount": 34804188582329,
"target": {
"tagged_key": {
"key": "5984a8e8ecabd0944f3e850631f633c2e5108bf9df8058932193a095146840c6",
"view_tag": "81"
}
}
}
],
"extra": [ 1, 211, 62, 74, 120, 157, 7, 214, 243, 111, 150, 40, 132, 217, 204, 241, 193, 62, 44, 193, 240, 123, 179, 175, 9, 57, 50, 113, 4, 3, 195, 145, 8, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}