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: cd83d0ce70227b6fdc06eeb0fdbcb62666525ad75a73a99cf01648b4632a8ad1
Tx prefix hash: a3b2372b963a3e681221e85e92e21e8e719ffbf17ece401ab0c7391fb19a2b46
Tx public key: 329c78f7c75d80b3f0a1c6476f1e0c2cb7857d0cabcb6354c03d9521a516ec92
| Timestamp: 1779976962 | Timestamp [UTC]: 2026-05-28 14:02:42 | Age [y:d:h:m:s]: 00:011:11:33:15 |
| Block: 3891 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3995 | RingCT/type: yes/0 |
| Extra: 01329c78f7c75d80b3f0a1c6476f1e0c2cb7857d0cabcb6354c03d9521a516ec9202090000000626697be300 | ||
1 output(s) for total of 34.924284424524 HMNY
| stealth address | amount | amount idx | tag |
| 00: a7e5240f0e261eb9981c38a7351fda9bba7e75e990e1a8f1fff344d289857e38 | 34.924284424524 | 4766 of 0 | <34> |
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": 3951,
"vin": [ {
"gen": {
"height": 3891
}
}
],
"vout": [ {
"amount": 34924284424524,
"target": {
"tagged_key": {
"key": "a7e5240f0e261eb9981c38a7351fda9bba7e75e990e1a8f1fff344d289857e38",
"view_tag": "34"
}
}
}
],
"extra": [ 1, 50, 156, 120, 247, 199, 93, 128, 179, 240, 161, 198, 71, 111, 30, 12, 44, 183, 133, 125, 12, 171, 203, 99, 84, 192, 61, 149, 33, 165, 22, 236, 146, 2, 9, 0, 0, 0, 6, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}