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: dd9e401b3d70df5474e5c672a4fcc9ef995ccf32fdb28f4ff31a2e4637a22164
Tx prefix hash: dafa201734195e48bd07e9bd771782d47ba96d602c2c027f9401e3f5f0240460
Tx public key: deeb8d7f781a362b667f495aabf0a5a0c5b500986267fd5ecdf209724de99d2b
| Timestamp: 1781009629 | Timestamp [UTC]: 2026-06-09 12:53:49 | Age [y:d:h:m:s]: 00:005:22:20:11 |
| Block: 8578 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 167 | RingCT/type: yes/0 |
| Extra: 01deeb8d7f781a362b667f495aabf0a5a0c5b500986267fd5ecdf209724de99d2b020900000002e49593ff00 | ||
1 output(s) for total of 34.613461408421 HMNY
| stealth address | amount | amount idx | tag |
| 00: eedbb6ad3dea0b3a3ee5f0aadb3ab7922d6abdb44347b17b3bbb73c85f95d4f6 | 34.613461408421 | 10598 of 0 | <60> |
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": 8638,
"vin": [ {
"gen": {
"height": 8578
}
}
],
"vout": [ {
"amount": 34613461408421,
"target": {
"tagged_key": {
"key": "eedbb6ad3dea0b3a3ee5f0aadb3ab7922d6abdb44347b17b3bbb73c85f95d4f6",
"view_tag": "60"
}
}
}
],
"extra": [ 1, 222, 235, 141, 127, 120, 26, 54, 43, 102, 127, 73, 90, 171, 240, 165, 160, 197, 181, 0, 152, 98, 103, 253, 94, 205, 242, 9, 114, 77, 233, 157, 43, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}