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: 3f9a9ce539126861165db35d9b8f530b629096e186ff483a65eba68d4338d4fa
Tx prefix hash: a43f2334956bf1ca7b28614ea8b246dc6da758dee7c7e772c930acfef746dc5a
Tx public key: f626fcc53d1a250773f178401494a71d2205accf6888e87200bafe1847d8c26b
| Timestamp: 1780693341 | Timestamp [UTC]: 2026-06-05 21:02:21 | Age [y:d:h:m:s]: 00:003:02:16:32 |
| Block: 5864 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2022 | RingCT/type: yes/0 |
| Extra: 01f626fcc53d1a250773f178401494a71d2205accf6888e87200bafe1847d8c26b020900000001e49593ff00 | ||
1 output(s) for total of 34.793104255690 HMNY
| stealth address | amount | amount idx | tag |
| 00: e0645a3f107295a6b4a80a77b2f231760a1e1dcedc9af19287796f600228e199 | 34.793104255690 | 7323 of 0 | <ce> |
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": 5924,
"vin": [ {
"gen": {
"height": 5864
}
}
],
"vout": [ {
"amount": 34793104255690,
"target": {
"tagged_key": {
"key": "e0645a3f107295a6b4a80a77b2f231760a1e1dcedc9af19287796f600228e199",
"view_tag": "ce"
}
}
}
],
"extra": [ 1, 246, 38, 252, 197, 61, 26, 37, 7, 115, 241, 120, 64, 20, 148, 167, 29, 34, 5, 172, 207, 104, 136, 232, 114, 0, 186, 254, 24, 71, 216, 194, 107, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}