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: 6552eaf4c1aaef5345015fde23500b36ba0a3f07254b1d2069af4c1e3c1395bb
Tx prefix hash: 3cfd973c3b55ea3687f26ff1050e2e3058d773ca9a33712c40b12f6755240029
Tx public key: 2ba1ffcd62404e455c10e8a13aad7eaad9cfcd8c492ace7cc81b72cbea1871b8
| Timestamp: 1779437942 | Timestamp [UTC]: 2026-05-22 08:19:02 | Age [y:d:h:m:s]: 00:017:18:30:46 |
| Block: 180 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7740 | RingCT/type: yes/0 |
| Extra: 012ba1ffcd62404e455c10e8a13aad7eaad9cfcd8c492ace7cc81b72cbea1871b8020900000002a662ed0300 | ||
1 output(s) for total of 35.172361641228 HMNY
| stealth address | amount | amount idx | tag |
| 00: b46ced8151dcdcff5666e588662eb86600c1fb6b4a474e07bc648536ac88c650 | 35.172361641228 | 176 of 0 | <7a> |
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": 240,
"vin": [ {
"gen": {
"height": 180
}
}
],
"vout": [ {
"amount": 35172361641228,
"target": {
"tagged_key": {
"key": "b46ced8151dcdcff5666e588662eb86600c1fb6b4a474e07bc648536ac88c650",
"view_tag": "7a"
}
}
}
],
"extra": [ 1, 43, 161, 255, 205, 98, 64, 78, 69, 92, 16, 232, 161, 58, 173, 126, 170, 217, 207, 205, 140, 73, 42, 206, 124, 200, 27, 114, 203, 234, 24, 113, 184, 2, 9, 0, 0, 0, 2, 166, 98, 237, 3, 0
],
"rct_signatures": {
"type": 0
}
}