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: fae2c0041f455283f713ca7831d28cff1d8699f32830dc626ab738fd67094222
Tx prefix hash: 92a904957581030aea380032ad2e70321f2914b151419b42365e6e52ab3265a5
Tx public key: 6e94aef1554bfaafac55f3340beb41ec97f104540e363ba714204a65e1ad0e0e
| Timestamp: 1779916262 | Timestamp [UTC]: 2026-05-27 21:11:02 | Age [y:d:h:m:s]: 00:012:04:24:55 |
| Block: 3306 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4580 | RingCT/type: yes/0 |
| Extra: 016e94aef1554bfaafac55f3340beb41ec97f104540e363ba714204a65e1ad0e0e02090000000126697be300 | ||
1 output(s) for total of 34.963274690208 HMNY
| stealth address | amount | amount idx | tag |
| 00: be2acfe1fb94f621081ad698deb77dd617429bc5a93fffff4c61b01939a30644 | 34.963274690208 | 3972 of 0 | <38> |
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": 3366,
"vin": [ {
"gen": {
"height": 3306
}
}
],
"vout": [ {
"amount": 34963274690208,
"target": {
"tagged_key": {
"key": "be2acfe1fb94f621081ad698deb77dd617429bc5a93fffff4c61b01939a30644",
"view_tag": "38"
}
}
}
],
"extra": [ 1, 110, 148, 174, 241, 85, 75, 250, 175, 172, 85, 243, 52, 11, 235, 65, 236, 151, 241, 4, 84, 14, 54, 59, 167, 20, 32, 74, 101, 225, 173, 14, 14, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}