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: c214e3757012eb22f1f8cb7e27426a9be5640bc7bf3b75d2d926414716bf68b6
Tx prefix hash: 105c5863e1f92ed1def906a4345ed030620ac29219df3fbd6232c1c43d5753ad
Tx public key: e5c3ae4b528288bfd9668cd8371cb5e3e6fdf501e3c00e9aed8a600bc9eb9e9d
| Timestamp: 1780688273 | Timestamp [UTC]: 2026-06-05 19:37:53 | Age [y:d:h:m:s]: 00:003:07:11:55 |
| Block: 5519 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2401 | RingCT/type: yes/0 |
| Extra: 01e5c3ae4b528288bfd9668cd8371cb5e3e6fdf501e3c00e9aed8a600bc9eb9e9d020900000001e49593ff00 | ||
1 output(s) for total of 34.816006902122 HMNY
| stealth address | amount | amount idx | tag |
| 00: caefc89c4068337a2456f5aad3ee89d81676278f00dab191e09549a14b61129c | 34.816006902122 | 6960 of 0 | <63> |
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": 5579,
"vin": [ {
"gen": {
"height": 5519
}
}
],
"vout": [ {
"amount": 34816006902122,
"target": {
"tagged_key": {
"key": "caefc89c4068337a2456f5aad3ee89d81676278f00dab191e09549a14b61129c",
"view_tag": "63"
}
}
}
],
"extra": [ 1, 229, 195, 174, 75, 82, 130, 136, 191, 217, 102, 140, 216, 55, 28, 181, 227, 230, 253, 245, 1, 227, 192, 14, 154, 237, 138, 96, 11, 201, 235, 158, 157, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}