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: 42bd0f4a26827a3a51064bd01c3732a13f72578c75980b0c3aa89d9f327dd2ee
Tx prefix hash: f2d8f604dc95a43da105e7888a6b5d95f3112c5e5b30e2af7bd7f14c84c6f1b7
Tx public key: 5e7f19645fc98b49d984fed7d475bbdacca4273738c4192bb2e6ce2484f6734e
| Timestamp: 1780997163 | Timestamp [UTC]: 2026-06-09 09:26:03 | Age [y:d:h:m:s]: 00:000:05:22:52 |
| Block: 8369 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 273 | RingCT/type: yes/0 |
| Extra: 015e7f19645fc98b49d984fed7d475bbdacca4273738c4192bb2e6ce2484f6734e020900000001e49593ff00 | ||
1 output(s) for total of 34.627262339277 HMNY
| stealth address | amount | amount idx | tag |
| 00: da25180a33ee25d11d72de783091610da5fd955cca1175adda7065d43b639535 | 34.627262339277 | 10347 of 0 | <84> |
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": 8429,
"vin": [ {
"gen": {
"height": 8369
}
}
],
"vout": [ {
"amount": 34627262339277,
"target": {
"tagged_key": {
"key": "da25180a33ee25d11d72de783091610da5fd955cca1175adda7065d43b639535",
"view_tag": "84"
}
}
}
],
"extra": [ 1, 94, 127, 25, 100, 95, 201, 139, 73, 217, 132, 254, 215, 212, 117, 187, 218, 204, 164, 39, 55, 56, 196, 25, 43, 178, 230, 206, 36, 132, 246, 115, 78, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}