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: d696220073c6e672a5676c8e447dd75ca23447e16a208647285fac77118a9c86
Tx prefix hash: a695e6ebb35f072ebe9dc6b13ccb2d3c4bcee8270b4f05c3f63da4ce49d9b320
Tx public key: 90dfeaf9fb86c640782b5555f290973d13307302eb7a96efcaf017122b705a0c
| Timestamp: 1780393593 | Timestamp [UTC]: 2026-06-02 09:46:33 | Age [y:d:h:m:s]: 00:006:15:00:14 |
| Block: 5227 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2659 | RingCT/type: yes/0 |
| Extra: 0190dfeaf9fb86c640782b5555f290973d13307302eb7a96efcaf017122b705a0c02090000000226697be300 | ||
1 output(s) for total of 34.835402950236 HMNY
| stealth address | amount | amount idx | tag |
| 00: e20ca1ab09b7f5ee843c84b199d2fd4f64f9a1681d46da66992288d669609d50 | 34.835402950236 | 6616 of 0 | <2c> |
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": 5287,
"vin": [ {
"gen": {
"height": 5227
}
}
],
"vout": [ {
"amount": 34835402950236,
"target": {
"tagged_key": {
"key": "e20ca1ab09b7f5ee843c84b199d2fd4f64f9a1681d46da66992288d669609d50",
"view_tag": "2c"
}
}
}
],
"extra": [ 1, 144, 223, 234, 249, 251, 134, 198, 64, 120, 43, 85, 85, 242, 144, 151, 61, 19, 48, 115, 2, 235, 122, 150, 239, 202, 240, 23, 18, 43, 112, 90, 12, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}