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: 1a4b1bcc2f0556d6a99bf32df67dd4e9314168539dbf5a15f99756a6e27fc3e6
Tx prefix hash: 0c62a05850681bfe7b43a8d7794fc5d0092ebb4a6143099d062d99710c2135cd
Tx public key: 1f82c56866c0a84013424f61a8715195b8a792f8a62fdf0d64f1d3332c33523c
| Timestamp: 1779799181 | Timestamp [UTC]: 2026-05-26 12:39:41 | Age [y:d:h:m:s]: 00:013:14:10:07 |
| Block: 2290 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5630 | RingCT/type: yes/0 |
| Extra: 011f82c56866c0a84013424f61a8715195b8a792f8a62fdf0d64f1d3332c33523c02090000000426697be300 | ||
1 output(s) for total of 35.031094595260 HMNY
| stealth address | amount | amount idx | tag |
| 00: defc773ebd03a7aaf5fa12b3a43a0483d69a860ac8b6915359a5a7b1f057ea39 | 35.031094595260 | 2670 of 0 | <76> |
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": 2350,
"vin": [ {
"gen": {
"height": 2290
}
}
],
"vout": [ {
"amount": 35031094595260,
"target": {
"tagged_key": {
"key": "defc773ebd03a7aaf5fa12b3a43a0483d69a860ac8b6915359a5a7b1f057ea39",
"view_tag": "76"
}
}
}
],
"extra": [ 1, 31, 130, 197, 104, 102, 192, 168, 64, 19, 66, 79, 97, 168, 113, 81, 149, 184, 167, 146, 248, 166, 47, 223, 13, 100, 241, 211, 51, 44, 51, 82, 60, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}