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: 70736441b249b110075aa3f20745c111e270c9d22bbf1768de74ec8eee8da5a2
Tx prefix hash: dc18d9bec71ca7e02257855dbf0c6ac8cb78e429cb345e9a41b45822b52b9083
Tx public key: 09daa2330aefee50feb898ebc1dc68673f8e6499242a761c6fb48dd278fba4ba
| Timestamp: 1779871309 | Timestamp [UTC]: 2026-05-27 08:41:49 | Age [y:d:h:m:s]: 00:012:18:57:01 |
| Block: 2813 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5131 | RingCT/type: yes/0 |
| Extra: 0109daa2330aefee50feb898ebc1dc68673f8e6499242a761c6fb48dd278fba4ba02090000000226697be300 | ||
1 output(s) for total of 34.996166950836 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5553aa0b99aa322a664f9a662bb26bb35bb7c1adaf757c489a9ca62595a3c87c | 34.996166950836 | 3329 of 0 | <cc> |
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": 2873,
"vin": [ {
"gen": {
"height": 2813
}
}
],
"vout": [ {
"amount": 34996166950836,
"target": {
"tagged_key": {
"key": "5553aa0b99aa322a664f9a662bb26bb35bb7c1adaf757c489a9ca62595a3c87c",
"view_tag": "cc"
}
}
}
],
"extra": [ 1, 9, 218, 162, 51, 10, 239, 238, 80, 254, 184, 152, 235, 193, 220, 104, 103, 63, 142, 100, 153, 36, 42, 118, 28, 111, 180, 141, 210, 120, 251, 164, 186, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}