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: 234d8f1c241856b44d3618453bf7ffed7be942051ce3b94710bf3c4f944de2fe
Tx prefix hash: e0c24caf59e3018f9701ea60684cc99eb4c24ff4911b30ce7d11a0ab68824afd
Tx public key: 5d7a27358bc6381fa211a6f02bc0d6c12fbdb6e9bd69154e4ca3a3505fc11b53
| Timestamp: 1779858627 | Timestamp [UTC]: 2026-05-27 05:10:27 | Age [y:d:h:m:s]: 00:012:22:40:31 |
| Block: 2649 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5304 | RingCT/type: yes/0 |
| Extra: 015d7a27358bc6381fa211a6f02bc0d6c12fbdb6e9bd69154e4ca3a3505fc11b5302090000000126697be300 | ||
1 output(s) for total of 35.007115655749 HMNY
| stealth address | amount | amount idx | tag |
| 00: 384012b21406a78558c2747579b14b97e7a9435b1b6a31a39952cc63a75af693 | 35.007115655749 | 3123 of 0 | <62> |
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": 2709,
"vin": [ {
"gen": {
"height": 2649
}
}
],
"vout": [ {
"amount": 35007115655749,
"target": {
"tagged_key": {
"key": "384012b21406a78558c2747579b14b97e7a9435b1b6a31a39952cc63a75af693",
"view_tag": "62"
}
}
}
],
"extra": [ 1, 93, 122, 39, 53, 139, 198, 56, 31, 162, 17, 166, 240, 43, 192, 214, 193, 47, 189, 182, 233, 189, 105, 21, 78, 76, 163, 163, 80, 95, 193, 27, 83, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}