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: 9ffa5a20863d5f0bd37ea750f16715abdd6086157dfa4c5e0576c0cf5bf351cc
Tx prefix hash: b83961c8fa2287b2b1382c99b08e913646af4850453a4fbe0112db7a06aa8fdc
Tx public key: ee3cf30a5c920f2cef941612354fe5f486cc8cc97f2c6539e198d98e58dae728
| Timestamp: 1780722617 | Timestamp [UTC]: 2026-06-06 05:10:17 | Age [y:d:h:m:s]: 00:007:05:51:59 |
| Block: 6257 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2488 | RingCT/type: yes/0 |
| Extra: 01ee3cf30a5c920f2cef941612354fe5f486cc8cc97f2c6539e198d98e58dae728020900000006e49593ff00 | ||
1 output(s) for total of 34.767033509332 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7fdf367c9f1754ea840183dffbfab8f0c8d518d6e478a8cbb9fc0df92b983779 | 34.767033509332 | 7738 of 0 | <0c> |
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": 6317,
"vin": [ {
"gen": {
"height": 6257
}
}
],
"vout": [ {
"amount": 34767033509332,
"target": {
"tagged_key": {
"key": "7fdf367c9f1754ea840183dffbfab8f0c8d518d6e478a8cbb9fc0df92b983779",
"view_tag": "0c"
}
}
}
],
"extra": [ 1, 238, 60, 243, 10, 92, 146, 15, 44, 239, 148, 22, 18, 53, 79, 229, 244, 134, 204, 140, 201, 127, 44, 101, 57, 225, 152, 217, 142, 88, 218, 231, 40, 2, 9, 0, 0, 0, 6, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}