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: cb8787d7c8db17f9582d9eec25a9f1fb7ec5f474fee183de75a589cfc6988495
Tx prefix hash: 01c6e95b5029ac2c7b0c06d530aeec151bca355ac05eaf814107943d392f595f
Tx public key: 71cd659dc398ab6b69d91f398a8ae719f7aac2da2540d387af87ced692e62bde
| Timestamp: 1779906320 | Timestamp [UTC]: 2026-05-27 18:25:20 | Age [y:d:h:m:s]: 00:016:16:36:56 |
| Block: 3194 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5551 | RingCT/type: yes/0 |
| Extra: 0171cd659dc398ab6b69d91f398a8ae719f7aac2da2540d387af87ced692e62bde02090000000126697be300 | ||
1 output(s) for total of 34.970744456429 HMNY
| stealth address | amount | amount idx | tag |
| 00: 74883cafc7b333e2790d6343e0ef657d9d64d4c56e66d5af6ec67cd6ac7c0609 | 34.970744456429 | 3826 of 0 | <51> |
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": 3254,
"vin": [ {
"gen": {
"height": 3194
}
}
],
"vout": [ {
"amount": 34970744456429,
"target": {
"tagged_key": {
"key": "74883cafc7b333e2790d6343e0ef657d9d64d4c56e66d5af6ec67cd6ac7c0609",
"view_tag": "51"
}
}
}
],
"extra": [ 1, 113, 205, 101, 157, 195, 152, 171, 107, 105, 217, 31, 57, 138, 138, 231, 25, 247, 170, 194, 218, 37, 64, 211, 135, 175, 135, 206, 214, 146, 230, 43, 222, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}