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: d9768e9740b1369f43cd4adeacf32b7a1ae5f3a365a854a7ec029345ede0f5ab
Tx prefix hash: 0fa1627a8e5a59c350003dc8d178b2ab61c7ae5a0d5482af8ba9e728395de246
Tx public key: e13d1df6fd404616aad7c869d37ead82ca479a30ae023ff2d6aaf0197e039fd0
| Timestamp: 1780814374 | Timestamp [UTC]: 2026-06-07 06:39:34 | Age [y:d:h:m:s]: 00:001:16:39:19 |
| Block: 7037 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 849 | RingCT/type: yes/0 |
| Extra: 01e13d1df6fd404616aad7c869d37ead82ca479a30ae023ff2d6aaf0197e039fd0020900000002e49593ff00 | ||
1 output(s) for total of 34.729183890759 HMNY
| stealth address | amount | amount idx | tag |
| 00: c7f8c3f10f74dc577b8f41317e917cf79410160d72b95758859f841e57c5568a | 34.729183890759 | 8677 of 0 | <7e> |
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": 7097,
"vin": [ {
"gen": {
"height": 7037
}
}
],
"vout": [ {
"amount": 34729183890759,
"target": {
"tagged_key": {
"key": "c7f8c3f10f74dc577b8f41317e917cf79410160d72b95758859f841e57c5568a",
"view_tag": "7e"
}
}
}
],
"extra": [ 1, 225, 61, 29, 246, 253, 64, 70, 22, 170, 215, 200, 105, 211, 126, 173, 130, 202, 71, 154, 48, 174, 2, 63, 242, 214, 170, 240, 25, 126, 3, 159, 208, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}