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: be438c6327ae175ce86971c26bc55cbff55958f57ed2cd8ce270ebc5637055e7
Tx prefix hash: 94f711a4a67bcf5994bad9f7f136093731721ba9b96f5963781842a322a264df
Tx public key: 0c933c81ad0812449d3e2a0fb81767bd9d0627a69709bfb410cb26a7e930206c
| Timestamp: 1780323259 | Timestamp [UTC]: 2026-06-01 14:14:19 | Age [y:d:h:m:s]: 00:007:10:32:28 |
| Block: 5090 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2796 | RingCT/type: yes/0 |
| Extra: 010c933c81ad0812449d3e2a0fb81767bd9d0627a69709bfb410cb26a7e930206c02090000002e26697be300 | ||
1 output(s) for total of 34.844506874697 HMNY
| stealth address | amount | amount idx | tag |
| 00: 1bdf21acbdb78aa73418e228c73f53287d6b7eaa8f93996a84581e855e476694 | 34.844506874697 | 6465 of 0 | <4e> |
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": 5150,
"vin": [ {
"gen": {
"height": 5090
}
}
],
"vout": [ {
"amount": 34844506874697,
"target": {
"tagged_key": {
"key": "1bdf21acbdb78aa73418e228c73f53287d6b7eaa8f93996a84581e855e476694",
"view_tag": "4e"
}
}
}
],
"extra": [ 1, 12, 147, 60, 129, 173, 8, 18, 68, 157, 62, 42, 15, 184, 23, 103, 189, 157, 6, 39, 166, 151, 9, 191, 180, 16, 203, 38, 167, 233, 48, 32, 108, 2, 9, 0, 0, 0, 46, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}