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: 6830784e879624468b296ef43d2b7bf53a8bc019e901d5394ad888c011bb2527
Tx prefix hash: 4e5364ba817a0291cb291b085b94f0080c32a63b5f5ec2bd5dca0f2bd789584b
Tx public key: e20d755533881b66b25621fea97dc77da6fab711305cc7892a9bbd72d690494b
| Timestamp: 1780732481 | Timestamp [UTC]: 2026-06-06 07:54:41 | Age [y:d:h:m:s]: 00:011:00:41:33 |
| Block: 6330 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2415 | RingCT/type: yes/0 |
| Extra: 01e20d755533881b66b25621fea97dc77da6fab711305cc7892a9bbd72d690494b020900000002e49593ff00 | ||
1 output(s) for total of 34.762193003382 HMNY
| stealth address | amount | amount idx | tag |
| 00: bece634e90ea7c78d22c70458fc6c7a0c02d5bd959df4ff061e3a0291dd8fda4 | 34.762193003382 | 7817 of 0 | <42> |
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": 6390,
"vin": [ {
"gen": {
"height": 6330
}
}
],
"vout": [ {
"amount": 34762193003382,
"target": {
"tagged_key": {
"key": "bece634e90ea7c78d22c70458fc6c7a0c02d5bd959df4ff061e3a0291dd8fda4",
"view_tag": "42"
}
}
}
],
"extra": [ 1, 226, 13, 117, 85, 51, 136, 27, 102, 178, 86, 33, 254, 169, 125, 199, 125, 166, 250, 183, 17, 48, 92, 199, 137, 42, 155, 189, 114, 214, 144, 73, 75, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}