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: 4022b53ac6301b056345324d0df32dcb27d1322d623ffd491c9ff4b6287f3df0
Tx prefix hash: 17b4754ae9f71844e3809c769a02232698e1f464ec4d9d060ffd2402b9f9ecec
Tx public key: 82ce762b46cbe16fe9479b7f638063e3d4f582ec8dfe226fb209fd82b2ee1a27
| Timestamp: 1780735588 | Timestamp [UTC]: 2026-06-06 08:46:28 | Age [y:d:h:m:s]: 00:002:16:49:29 |
| Block: 6362 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1524 | RingCT/type: yes/0 |
| Extra: 0182ce762b46cbe16fe9479b7f638063e3d4f582ec8dfe226fb209fd82b2ee1a27020900000003e49593ff00 | ||
1 output(s) for total of 34.760071350225 HMNY
| stealth address | amount | amount idx | tag |
| 00: 542e16a80303306d6618aee2ff9c3d1dfbcac149ef31ff3289d5f39bf6defce6 | 34.760071350225 | 7851 of 0 | <a6> |
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": 6422,
"vin": [ {
"gen": {
"height": 6362
}
}
],
"vout": [ {
"amount": 34760071350225,
"target": {
"tagged_key": {
"key": "542e16a80303306d6618aee2ff9c3d1dfbcac149ef31ff3289d5f39bf6defce6",
"view_tag": "a6"
}
}
}
],
"extra": [ 1, 130, 206, 118, 43, 70, 203, 225, 111, 233, 71, 155, 127, 99, 128, 99, 227, 212, 245, 130, 236, 141, 254, 34, 111, 178, 9, 253, 130, 178, 238, 26, 39, 2, 9, 0, 0, 0, 3, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}