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: 23259812291a87ee1c3375e72f811a9e6dacc0df110b24c6661ef1eaf792e30f
Tx prefix hash: d341ce15c7919e6b7d16f2011dc387d6831c9332c38a6bb5c8d5f04abd677ca6
Tx public key: fa3279df778c8bec914b567a5ed2808244cec3b1da08c8c413fecde0a1b804d4
| Timestamp: 1780860744 | Timestamp [UTC]: 2026-06-07 19:32:24 | Age [y:d:h:m:s]: 00:001:07:17:24 |
| Block: 7614 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 306 | RingCT/type: yes/0 |
| Extra: 01fa3279df778c8bec914b567a5ed2808244cec3b1da08c8c413fecde0a1b804d4020900000002e49593ff00 | ||
1 output(s) for total of 34.677163235509 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8d579a71af560313cdbfcea5bef037fa480d856d80668bcc064e34d635a3a129 | 34.677163235509 | 9410 of 0 | <ab> |
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": 7674,
"vin": [ {
"gen": {
"height": 7614
}
}
],
"vout": [ {
"amount": 34677163235509,
"target": {
"tagged_key": {
"key": "8d579a71af560313cdbfcea5bef037fa480d856d80668bcc064e34d635a3a129",
"view_tag": "ab"
}
}
}
],
"extra": [ 1, 250, 50, 121, 223, 119, 140, 139, 236, 145, 75, 86, 122, 94, 210, 128, 130, 68, 206, 195, 177, 218, 8, 200, 196, 19, 254, 205, 224, 161, 184, 4, 212, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}