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: c09a9a22f733629e71fd244d8c537dc6a8fa6bac3965a4c0441bdf4c1f9b1e2b
Tx prefix hash: 437cfa0fc0b6ead083c465dbdc2652f022b9a8fb735cf8d4e3fe49c62cc717e5
Tx public key: 63bf56bc9d0629643beef7b775b3f19012158afee6f553444416137a39d1f48c
| Timestamp: 1780047023 | Timestamp [UTC]: 2026-05-29 09:30:23 | Age [y:d:h:m:s]: 00:010:15:16:24 |
| Block: 4354 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3532 | RingCT/type: yes/0 |
| Extra: 0163bf56bc9d0629643beef7b775b3f19012158afee6f553444416137a39d1f48c02090000000126697be300 | ||
1 output(s) for total of 34.893456289340 HMNY
| stealth address | amount | amount idx | tag |
| 00: f85be43f9c4fd230e444bea4d28eb3fc0aff785207fe810269ce8b4580342a24 | 34.893456289340 | 5445 of 0 | <03> |
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": 4414,
"vin": [ {
"gen": {
"height": 4354
}
}
],
"vout": [ {
"amount": 34893456289340,
"target": {
"tagged_key": {
"key": "f85be43f9c4fd230e444bea4d28eb3fc0aff785207fe810269ce8b4580342a24",
"view_tag": "03"
}
}
}
],
"extra": [ 1, 99, 191, 86, 188, 157, 6, 41, 100, 59, 238, 247, 183, 117, 179, 241, 144, 18, 21, 138, 254, 230, 245, 83, 68, 68, 22, 19, 122, 57, 209, 244, 140, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}