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: b02e7f0c33b2bc8cc8fde204defb156b29ebf8ea1a26447bd22e18ab4208dd50
Tx prefix hash: 44e666700347a52c5350390c47281ca82e0fb99353afd84f031b59ce7fc4e279
Tx public key: 91ae1d7eaeca56d6e49d26697eeb1968467709c9dca303b260188b331bae3911
| Timestamp: 1780689623 | Timestamp [UTC]: 2026-06-05 20:00:23 | Age [y:d:h:m:s]: 00:007:15:01:53 |
| Block: 5607 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3138 | RingCT/type: yes/0 |
| Extra: 0191ae1d7eaeca56d6e49d26697eeb1968467709c9dca303b260188b331bae3911020900000001e49593ff00 | ||
1 output(s) for total of 34.810163635791 HMNY
| stealth address | amount | amount idx | tag |
| 00: dd91d19d6eae6980ed8d3339b5c8a55c046969f94b5597e1daf5d23d5beab3da | 34.810163635791 | 7054 of 0 | <7c> |
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": 5667,
"vin": [ {
"gen": {
"height": 5607
}
}
],
"vout": [ {
"amount": 34810163635791,
"target": {
"tagged_key": {
"key": "dd91d19d6eae6980ed8d3339b5c8a55c046969f94b5597e1daf5d23d5beab3da",
"view_tag": "7c"
}
}
}
],
"extra": [ 1, 145, 174, 29, 126, 174, 202, 86, 214, 228, 157, 38, 105, 126, 235, 25, 104, 70, 119, 9, 201, 220, 163, 3, 178, 96, 24, 139, 51, 27, 174, 57, 17, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}