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: d703df88f1ce50894477b9e4297bcd7670e9c575155045dd72f11a00d0b08502
Tx prefix hash: 3acf3ba6adacf09fa71d5856a2b66e896560d5c74df3b5c3ccb1d1014702ad44
Tx public key: 362f6205390801a10f341fe0d23e96c4b3a7df718b10c2ed4adb9880d4e241b9
| Timestamp: 1779957223 | Timestamp [UTC]: 2026-05-28 08:33:43 | Age [y:d:h:m:s]: 00:011:17:02:14 |
| Block: 3712 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4174 | RingCT/type: yes/0 |
| Extra: 01362f6205390801a10f341fe0d23e96c4b3a7df718b10c2ed4adb9880d4e241b902090000000326697be300 | ||
1 output(s) for total of 34.936210160317 HMNY
| stealth address | amount | amount idx | tag |
| 00: bc9ae43d32371503e91df20ffedff78484b1752544e1d7e664a3b25fc42db5e2 | 34.936210160317 | 4492 of 0 | <b0> |
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": 3772,
"vin": [ {
"gen": {
"height": 3712
}
}
],
"vout": [ {
"amount": 34936210160317,
"target": {
"tagged_key": {
"key": "bc9ae43d32371503e91df20ffedff78484b1752544e1d7e664a3b25fc42db5e2",
"view_tag": "b0"
}
}
}
],
"extra": [ 1, 54, 47, 98, 5, 57, 8, 1, 161, 15, 52, 31, 224, 210, 62, 150, 196, 179, 167, 223, 113, 139, 16, 194, 237, 74, 219, 152, 128, 212, 226, 65, 185, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}