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: d3513a7b9168b2a5dbfc766a960a8e0bf2f7f12c4b32fcf97157d325cc2dec38
Tx prefix hash: a50fdca48d987597b7bab1d83a702f2e97f634ec0df3e6256334d6fab0dc5dda
Tx public key: 746e12af3dc5e523248baec79ba2fe06d7a4e9d1ba531cd98335857a2ea7c84c
| Timestamp: 1779447461 | Timestamp [UTC]: 2026-05-22 10:57:41 | Age [y:d:h:m:s]: 00:017:12:21:12 |
| Block: 284 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7602 | RingCT/type: yes/0 |
| Extra: 01746e12af3dc5e523248baec79ba2fe06d7a4e9d1ba531cd98335857a2ea7c84c0209000000044438f87f00 | ||
1 output(s) for total of 35.165385387105 HMNY
| stealth address | amount | amount idx | tag |
| 00: c1233e3084bd6479583c28952f1029fa23af00f80cd4c9231f0d7fd7ee8f3beb | 35.165385387105 | 280 of 0 | <c7> |
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": 344,
"vin": [ {
"gen": {
"height": 284
}
}
],
"vout": [ {
"amount": 35165385387105,
"target": {
"tagged_key": {
"key": "c1233e3084bd6479583c28952f1029fa23af00f80cd4c9231f0d7fd7ee8f3beb",
"view_tag": "c7"
}
}
}
],
"extra": [ 1, 116, 110, 18, 175, 61, 197, 229, 35, 36, 139, 174, 199, 155, 162, 254, 6, 215, 164, 233, 209, 186, 83, 28, 217, 131, 53, 133, 122, 46, 167, 200, 76, 2, 9, 0, 0, 0, 4, 68, 56, 248, 127, 0
],
"rct_signatures": {
"type": 0
}
}