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: 2cb85c83d110141eb2e01d5a5da5416d4fbc9cfa5a5c70f9ebb2b875ecad47c2
Tx prefix hash: 4f0e4ba483836565d1f2a772c3f6d8b4aea021a608cccd27c4d2915a43e6b8e0
Tx public key: 9693477fec32d12d4d4b582c7ea9754cffd995d4a1df4550d4942c3122da0bb6
| Timestamp: 1780688186 | Timestamp [UTC]: 2026-06-05 19:36:26 | Age [y:d:h:m:s]: 00:003:21:32:37 |
| Block: 5512 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3222 | RingCT/type: yes/0 |
| Extra: 019693477fec32d12d4d4b582c7ea9754cffd995d4a1df4550d4942c3122da0bb6020900000001e49593ff00 | ||
1 output(s) for total of 34.816471749511 HMNY
| stealth address | amount | amount idx | tag |
| 00: 59e621c073262df2e2453502b2b054161e10f095f0ede2b8af856cf67b4c8f3f | 34.816471749511 | 6953 of 0 | <a5> |
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": 5572,
"vin": [ {
"gen": {
"height": 5512
}
}
],
"vout": [ {
"amount": 34816471749511,
"target": {
"tagged_key": {
"key": "59e621c073262df2e2453502b2b054161e10f095f0ede2b8af856cf67b4c8f3f",
"view_tag": "a5"
}
}
}
],
"extra": [ 1, 150, 147, 71, 127, 236, 50, 209, 45, 77, 75, 88, 44, 126, 169, 117, 76, 255, 217, 149, 212, 161, 223, 69, 80, 212, 148, 44, 49, 34, 218, 11, 182, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}