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: 837f4ee65cd193b346ba9a0781fe7e0f479ff76dcfd8a92a6bacc20c541607b9
Tx prefix hash: d730164f00494fc951041474fff3dcfb8dc9b96cb44813a0e9e6a8436f04312e
Tx public key: 8e0c0a1b6a82e357fbd490e9bdd5e8b357b682bf62f170126b8f69dbbbc9a4a2
| Timestamp: 1779886013 | Timestamp [UTC]: 2026-05-27 12:46:53 | Age [y:d:h:m:s]: 00:012:13:53:43 |
| Block: 3010 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4886 | RingCT/type: yes/0 |
| Extra: 018e0c0a1b6a82e357fbd490e9bdd5e8b357b682bf62f170126b8f69dbbbc9a4a202090000000426697be300 | ||
1 output(s) for total of 34.983019679917 HMNY
| stealth address | amount | amount idx | tag |
| 00: 536c45abd54730e6914d00d6f4d4cb4c4dc76594a2342723403df0bcee48db55 | 34.983019679917 | 3574 of 0 | <77> |
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": 3070,
"vin": [ {
"gen": {
"height": 3010
}
}
],
"vout": [ {
"amount": 34983019679917,
"target": {
"tagged_key": {
"key": "536c45abd54730e6914d00d6f4d4cb4c4dc76594a2342723403df0bcee48db55",
"view_tag": "77"
}
}
}
],
"extra": [ 1, 142, 12, 10, 27, 106, 130, 227, 87, 251, 212, 144, 233, 189, 213, 232, 179, 87, 182, 130, 191, 98, 241, 112, 18, 107, 143, 105, 219, 187, 201, 164, 162, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}