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: d3f51531f08be07a5ca5ab5b56b86309580a5f5f0d27780e893b1cd9f6306e10
Tx prefix hash: baade22ad13b84bd5a124ddd55c4e152b305fc463a14867d4c15df42d62334b6
Tx public key: 24301a1538dc7f76eb65c7e3a9fd39f8f85bfaca591ecf904edf33bc62a52cea
| Timestamp: 1780749726 | Timestamp [UTC]: 2026-06-06 12:42:06 | Age [y:d:h:m:s]: 00:010:19:23:15 |
| Block: 6480 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2265 | RingCT/type: yes/0 |
| Extra: 0124301a1538dc7f76eb65c7e3a9fd39f8f85bfaca591ecf904edf33bc62a52cea020900000001e49593ff00 | ||
1 output(s) for total of 34.752248873291 HMNY
| stealth address | amount | amount idx | tag |
| 00: b0c2722273f4d5c2239afeb38d3d6d20a5ce34162c479562cfd4ad534aa5616d | 34.752248873291 | 7975 of 0 | <85> |
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": 6540,
"vin": [ {
"gen": {
"height": 6480
}
}
],
"vout": [ {
"amount": 34752248873291,
"target": {
"tagged_key": {
"key": "b0c2722273f4d5c2239afeb38d3d6d20a5ce34162c479562cfd4ad534aa5616d",
"view_tag": "85"
}
}
}
],
"extra": [ 1, 36, 48, 26, 21, 56, 220, 127, 118, 235, 101, 199, 227, 169, 253, 57, 248, 248, 91, 250, 202, 89, 30, 207, 144, 78, 223, 51, 188, 98, 165, 44, 234, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}