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: f614ccbe1a757647f5f46ee7b7be7df784193261d6640ed0d9aa7449d9fc3f69
Tx prefix hash: 3588b2956cdf10bddea44bfa63439564cea957d944dff2aa398e961a8e6864f9
Tx public key: 369c42a6010bec73b1b7bb0a4f432b25a3ce4772f4872b08bb0390984223f940
| Timestamp: 1780035581 | Timestamp [UTC]: 2026-05-29 06:19:41 | Age [y:d:h:m:s]: 00:010:18:27:06 |
| Block: 4240 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3646 | RingCT/type: yes/0 |
| Extra: 01369c42a6010bec73b1b7bb0a4f432b25a3ce4772f4872b08bb0390984223f94002090000000426697be300 | ||
1 output(s) for total of 34.901044275925 HMNY
| stealth address | amount | amount idx | tag |
| 00: 74050b3997a48d12fa97f8b5f60c262f04de4d9119be2b05dc6d9508ec7d96ac | 34.901044275925 | 5291 of 0 | <73> |
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": 4300,
"vin": [ {
"gen": {
"height": 4240
}
}
],
"vout": [ {
"amount": 34901044275925,
"target": {
"tagged_key": {
"key": "74050b3997a48d12fa97f8b5f60c262f04de4d9119be2b05dc6d9508ec7d96ac",
"view_tag": "73"
}
}
}
],
"extra": [ 1, 54, 156, 66, 166, 1, 11, 236, 115, 177, 183, 187, 10, 79, 67, 43, 37, 163, 206, 71, 114, 244, 135, 43, 8, 187, 3, 144, 152, 66, 35, 249, 64, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}