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: 37df8d1b2b9a0be3bf0ee57a05125a9a5796e9d2a19619eaa87b0a45bf6a9cc1
Tx prefix hash: fab474499d3657dec029accb6e3d91d7eb4d4c572e9dec91e902b785eaf6ccf4
Tx public key: 5bd2a946a3619007231fd3b3b8b6a556360c84144e2750af2e7d7974e84d82fc
| Timestamp: 1780996717 | Timestamp [UTC]: 2026-06-09 09:18:37 | Age [y:d:h:m:s]: 00:000:09:03:15 |
| Block: 8357 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 388 | RingCT/type: yes/0 |
| Extra: 015bd2a946a3619007231fd3b3b8b6a556360c84144e2750af2e7d7974e84d82fc020900000001e49593ff00 | ||
1 output(s) for total of 34.628054904241 HMNY
| stealth address | amount | amount idx | tag |
| 00: 6d700d512a85d6b6ecfb11cd93d4184be155d957d541bc3627bce339893069b3 | 34.628054904241 | 10333 of 0 | <29> |
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": 8417,
"vin": [ {
"gen": {
"height": 8357
}
}
],
"vout": [ {
"amount": 34628054904241,
"target": {
"tagged_key": {
"key": "6d700d512a85d6b6ecfb11cd93d4184be155d957d541bc3627bce339893069b3",
"view_tag": "29"
}
}
}
],
"extra": [ 1, 91, 210, 169, 70, 163, 97, 144, 7, 35, 31, 211, 179, 184, 182, 165, 86, 54, 12, 132, 20, 78, 39, 80, 175, 46, 125, 121, 116, 232, 77, 130, 252, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}