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: 6293769e6e0fe492d834ee463ad4234afe561c8e0b00ff83b080c4f0176675f1
Tx prefix hash: 417c6a8c39c0ef3c8fcf7812506beea73519fb4b852c993edab68e636b0e3fdc
Tx public key: ee247db80c5e7f7a63d6b08b6d7e49a611647ed66a7d9bb4140f516a0ebf5cc5
| Timestamp: 1780683089 | Timestamp [UTC]: 2026-06-05 18:11:29 | Age [y:d:h:m:s]: 00:003:08:38:19 |
| Block: 5316 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2584 | RingCT/type: yes/0 |
| Extra: 01ee247db80c5e7f7a63d6b08b6d7e49a611647ed66a7d9bb4140f516a0ebf5cc5020900000002e49593ff00 | ||
1 output(s) for total of 34.829489996506 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9075df44826f2c816565fad7aaff08af284b88d1b9b4f59d58e647740cabfcc6 | 34.829489996506 | 6745 of 0 | <40> |
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": 5376,
"vin": [ {
"gen": {
"height": 5316
}
}
],
"vout": [ {
"amount": 34829489996506,
"target": {
"tagged_key": {
"key": "9075df44826f2c816565fad7aaff08af284b88d1b9b4f59d58e647740cabfcc6",
"view_tag": "40"
}
}
}
],
"extra": [ 1, 238, 36, 125, 184, 12, 94, 127, 122, 99, 214, 176, 139, 109, 126, 73, 166, 17, 100, 126, 214, 106, 125, 155, 180, 20, 15, 81, 106, 14, 191, 92, 197, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}