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: b18bbf361a725b40b0242eb8eac1c2e302688c21d1a50f0931f50dccc7ca58ab
Tx prefix hash: f1f217d046cedba6f59b6b8c737b7a6690966fc0268eefa4da4ec4ae54c2f9b5
Tx public key: 7fd8a5f6ead6c858c5a5dcd85ec04b40aa8c5a21bd68193f39c9be0ea5838173
| Timestamp: 1780082828 | Timestamp [UTC]: 2026-05-29 19:27:08 | Age [y:d:h:m:s]: 00:010:06:08:49 |
| Block: 4780 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3106 | RingCT/type: yes/0 |
| Extra: 017fd8a5f6ead6c858c5a5dcd85ec04b40aa8c5a21bd68193f39c9be0ea583817302090000000326697be300 | ||
1 output(s) for total of 34.865115779538 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2436708fdd1ec87b31c9b71ae846890ee796febf8ed10cc474dd1e54ec51145b | 34.865115779538 | 6009 of 0 | <58> |
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": 4840,
"vin": [ {
"gen": {
"height": 4780
}
}
],
"vout": [ {
"amount": 34865115779538,
"target": {
"tagged_key": {
"key": "2436708fdd1ec87b31c9b71ae846890ee796febf8ed10cc474dd1e54ec51145b",
"view_tag": "58"
}
}
}
],
"extra": [ 1, 127, 216, 165, 246, 234, 214, 200, 88, 197, 165, 220, 216, 94, 192, 75, 64, 170, 140, 90, 33, 189, 104, 25, 63, 57, 201, 190, 14, 165, 131, 129, 115, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}