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: 55809d0d55cc7914f4845e6c10d9807169e771efe817a34c3e515a270e1a5f6d
Tx prefix hash: 59c180fde9450ab3610c75e058dd62888950c9d74fea6c12eb8d42119af4e697
Tx public key: 58ce1a5deb2f36bf86f7bd36ff1fb5cc0fc011fa6df02a44b993a269e02c34d3
| Timestamp: 1779920696 | Timestamp [UTC]: 2026-05-27 22:24:56 | Age [y:d:h:m:s]: 00:012:04:24:52 |
| Block: 3352 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4568 | RingCT/type: yes/0 |
| Extra: 0158ce1a5deb2f36bf86f7bd36ff1fb5cc0fc011fa6df02a44b993a269e02c34d302090000000426697be300 | ||
1 output(s) for total of 34.960207212760 HMNY
| stealth address | amount | amount idx | tag |
| 00: 64896ae994fa37a8ecd460a01372cc148195d00e066eb54ad9346d7822c296e5 | 34.960207212760 | 4033 of 0 | <74> |
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": 3412,
"vin": [ {
"gen": {
"height": 3352
}
}
],
"vout": [ {
"amount": 34960207212760,
"target": {
"tagged_key": {
"key": "64896ae994fa37a8ecd460a01372cc148195d00e066eb54ad9346d7822c296e5",
"view_tag": "74"
}
}
}
],
"extra": [ 1, 88, 206, 26, 93, 235, 47, 54, 191, 134, 247, 189, 54, 255, 31, 181, 204, 15, 192, 17, 250, 109, 240, 42, 68, 185, 147, 162, 105, 224, 44, 52, 211, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}