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: 44c3e53cdd34a97cec345da7d28e6a9b1b06e3819f51a1d7cc9c3391836e82bd
Tx prefix hash: 916817878253aa2ee83a257fa34c86640939a49e3edfd543c15b993f453a8ed0
Tx public key: 16da6c0d79a15cc3dbe1da540a61203da421d6e1a5c70402eef4df5fd68e1e2c
| Timestamp: 1780684359 | Timestamp [UTC]: 2026-06-05 18:32:39 | Age [y:d:h:m:s]: 00:003:06:14:08 |
| Block: 5349 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2537 | RingCT/type: yes/0 |
| Extra: 0116da6c0d79a15cc3dbe1da540a61203da421d6e1a5c70402eef4df5fd68e1e2c020900000001e49593ff00 | ||
1 output(s) for total of 34.827297808063 HMNY
| stealth address | amount | amount idx | tag |
| 00: c7314e32b2f593f942dd8dba1a68fdc1ca0db22a946a516099856c07d63fad4a | 34.827297808063 | 6782 of 0 | <d5> |
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": 5409,
"vin": [ {
"gen": {
"height": 5349
}
}
],
"vout": [ {
"amount": 34827297808063,
"target": {
"tagged_key": {
"key": "c7314e32b2f593f942dd8dba1a68fdc1ca0db22a946a516099856c07d63fad4a",
"view_tag": "d5"
}
}
}
],
"extra": [ 1, 22, 218, 108, 13, 121, 161, 92, 195, 219, 225, 218, 84, 10, 97, 32, 61, 164, 33, 214, 225, 165, 199, 4, 2, 238, 244, 223, 95, 214, 142, 30, 44, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}