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: c61f95e02bf69e13f07e8bdaeb87dc6f1ff79cb54507dabab8055e55cab637b9
Tx prefix hash: 5feab3fc4827e0d242b4c4aede2e7b7f213179cea9082c780bdb7511354be3f1
Tx public key: 8b4c2a705e6a012b9e9596a4fc2fb86c0c529e3fadcbcc8df1fb702c80badd14
| Timestamp: 1780836826 | Timestamp [UTC]: 2026-06-07 12:53:46 | Age [y:d:h:m:s]: 00:001:14:45:04 |
| Block: 7419 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 523 | RingCT/type: yes/0 |
| Extra: 018b4c2a705e6a012b9e9596a4fc2fb86c0c529e3fadcbcc8df1fb702c80badd14020900000001e49593ff00 | ||
1 output(s) for total of 34.690063227407 HMNY
| stealth address | amount | amount idx | tag |
| 00: 097bd28edc644d157f76f2ee1dc2d655e54bea61292466411e049149830440b5 | 34.690063227407 | 9135 of 0 | <2e> |
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": 7479,
"vin": [ {
"gen": {
"height": 7419
}
}
],
"vout": [ {
"amount": 34690063227407,
"target": {
"tagged_key": {
"key": "097bd28edc644d157f76f2ee1dc2d655e54bea61292466411e049149830440b5",
"view_tag": "2e"
}
}
}
],
"extra": [ 1, 139, 76, 42, 112, 94, 106, 1, 43, 158, 149, 150, 164, 252, 47, 184, 108, 12, 82, 158, 63, 173, 203, 204, 141, 241, 251, 112, 44, 128, 186, 221, 20, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}