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: 6cbe1e033b8e4bea5ec76d43ade9bb1e333045630b381083c8f0d95d0d5c9a2d
Tx prefix hash: 2215fe60c632509b2798d28d88a35df3d501fd5410dd7b086a8dfa06ba53d5c1
Tx public key: 914627d465e809d742f88783968b82c3b7622c27f556c415ea92f5d7c6a3e3fc
| Timestamp: 1779630061 | Timestamp [UTC]: 2026-05-24 13:41:01 | Age [y:d:h:m:s]: 00:015:13:57:49 |
| Block: 858 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7086 | RingCT/type: yes/0 |
| Extra: 01914627d465e809d742f88783968b82c3b7622c27f556c415ea92f5d7c6a3e3fc020900000002ba6d17be00 | ||
1 output(s) for total of 35.126906716874 HMNY
| stealth address | amount | amount idx | tag |
| 00: d61389acd1d36bf4b8e9f84de37e63e4c6816fb879b93f7d45e44bfcf5b38807 | 35.126906716874 | 990 of 0 | <24> |
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": 918,
"vin": [ {
"gen": {
"height": 858
}
}
],
"vout": [ {
"amount": 35126906716874,
"target": {
"tagged_key": {
"key": "d61389acd1d36bf4b8e9f84de37e63e4c6816fb879b93f7d45e44bfcf5b38807",
"view_tag": "24"
}
}
}
],
"extra": [ 1, 145, 70, 39, 212, 101, 232, 9, 215, 66, 248, 135, 131, 150, 139, 130, 195, 183, 98, 44, 39, 245, 86, 196, 21, 234, 146, 245, 215, 198, 163, 227, 252, 2, 9, 0, 0, 0, 2, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}