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: 98041aeb975bca3a50b2febb3a9792a597da3f061865f002b37241e8e489663b
Tx prefix hash: 8d94f43d114bc404f059451a56a25f8b4db3a39ecfd8abd80abbd7b15f64d037
Tx public key: 6dedec6fa30b2b49ea2b0fb2324fd7c514398edbcb7a1d5db74b0c7d1c9be02f
| Timestamp: 1780018199 | Timestamp [UTC]: 2026-05-29 01:29:59 | Age [y:d:h:m:s]: 00:010:23:16:48 |
| Block: 4129 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3757 | RingCT/type: yes/0 |
| Extra: 016dedec6fa30b2b49ea2b0fb2324fd7c514398edbcb7a1d5db74b0c7d1c9be02f02090000000126697be300 | ||
1 output(s) for total of 34.911050164181 HMNY
| stealth address | amount | amount idx | tag |
| 00: 81955ce271e582d6fb83aecfce4c15652abb6c3247d6907bfd3c928e9631bd0e | 34.911050164181 | 5154 of 0 | <3e> |
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": 4189,
"vin": [ {
"gen": {
"height": 4129
}
}
],
"vout": [ {
"amount": 34911050164181,
"target": {
"tagged_key": {
"key": "81955ce271e582d6fb83aecfce4c15652abb6c3247d6907bfd3c928e9631bd0e",
"view_tag": "3e"
}
}
}
],
"extra": [ 1, 109, 237, 236, 111, 163, 11, 43, 73, 234, 43, 15, 178, 50, 79, 215, 197, 20, 57, 142, 219, 203, 122, 29, 93, 183, 75, 12, 125, 28, 155, 224, 47, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}