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: a0e77c493ff733d8b53f43c1bd2ce33661dbdfcaf5328a9522f74528d3d10a8e
Tx prefix hash: 74de24bcadabdcac94ee1bed5d226dd4097e16f9b2bc9c7a7bd468f758fbe1c8
Tx public key: 0c386d1204078d97cfecfb3d6600a63b221267ade36de749d5b633e550bc1f85
| Timestamp: 1780984873 | Timestamp [UTC]: 2026-06-09 06:01:13 | Age [y:d:h:m:s]: 00:000:08:47:42 |
| Block: 8124 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 518 | RingCT/type: yes/0 |
| Extra: 010c386d1204078d97cfecfb3d6600a63b221267ade36de749d5b633e550bc1f85020900000001e49593ff00 | ||
1 output(s) for total of 34.643447470140 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8bc3e08e2b1b5c3ef9b2c47e9ce8069a40d99f001ad53b59a912165cc260af3f | 34.643447470140 | 10062 of 0 | <ff> |
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": 8184,
"vin": [ {
"gen": {
"height": 8124
}
}
],
"vout": [ {
"amount": 34643447470140,
"target": {
"tagged_key": {
"key": "8bc3e08e2b1b5c3ef9b2c47e9ce8069a40d99f001ad53b59a912165cc260af3f",
"view_tag": "ff"
}
}
}
],
"extra": [ 1, 12, 56, 109, 18, 4, 7, 141, 151, 207, 236, 251, 61, 102, 0, 166, 59, 34, 18, 103, 173, 227, 109, 231, 73, 213, 182, 51, 229, 80, 188, 31, 133, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}