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: f2516f378a0497dc6de391551e61bbd1cf5be88a84c73a8fc4c2a485c366622c
Tx prefix hash: 5aa4d6e9cad55cf01ffb45a98288de9c28ea961e8b61b03d22bd161af15114a1
Tx public key: 6d1a1d1aef946f0e10c673cc146e852a345776c797cbee1e6262d2532eef6a96
| Timestamp: 1779708555 | Timestamp [UTC]: 2026-05-25 11:29:15 | Age [y:d:h:m:s]: 00:014:14:06:42 |
| Block: 1569 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6317 | RingCT/type: yes/0 |
| Extra: 016d1a1d1aef946f0e10c673cc146e852a345776c797cbee1e6262d2532eef6a96020900000003ba6d17be00 | ||
1 output(s) for total of 35.079302485328 HMNY
| stealth address | amount | amount idx | tag |
| 00: fdf34b9811fa29bb324c3b839a461aecf6e247a68391a11db806befa501572b8 | 35.079302485328 | 1727 of 0 | <db> |
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": 1629,
"vin": [ {
"gen": {
"height": 1569
}
}
],
"vout": [ {
"amount": 35079302485328,
"target": {
"tagged_key": {
"key": "fdf34b9811fa29bb324c3b839a461aecf6e247a68391a11db806befa501572b8",
"view_tag": "db"
}
}
}
],
"extra": [ 1, 109, 26, 29, 26, 239, 148, 111, 14, 16, 198, 115, 204, 20, 110, 133, 42, 52, 87, 118, 199, 151, 203, 238, 30, 98, 98, 210, 83, 46, 239, 106, 150, 2, 9, 0, 0, 0, 3, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}