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: 46cc97caa69b16ab1fb3c78a0babad424ea8b204f51eae53a7c50f4f0eaa3487
Tx prefix hash: 1019db27db94091648d7964d037efa5a3a0e3b3359dce1b96d77e4ec461c42d7
Tx public key: d64c80e8dc5f39dddb63b1a6efbebf7ce3b3c22e1a224e0b2f8c7e67155656b1
| Timestamp: 1779960511 | Timestamp [UTC]: 2026-05-28 09:28:31 | Age [y:d:h:m:s]: 00:011:15:18:16 |
| Block: 3750 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4136 | RingCT/type: yes/0 |
| Extra: 01d64c80e8dc5f39dddb63b1a6efbebf7ce3b3c22e1a224e0b2f8c7e67155656b102090000000326697be300 | ||
1 output(s) for total of 34.940996899422 HMNY
| stealth address | amount | amount idx | tag |
| 00: 034985d2becf1417208dfc0096c02ab58af307e8ff131f49607af85db5352dae | 34.940996899422 | 4545 of 0 | <ed> |
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": 3810,
"vin": [ {
"gen": {
"height": 3750
}
}
],
"vout": [ {
"amount": 34940996899422,
"target": {
"tagged_key": {
"key": "034985d2becf1417208dfc0096c02ab58af307e8ff131f49607af85db5352dae",
"view_tag": "ed"
}
}
}
],
"extra": [ 1, 214, 76, 128, 232, 220, 95, 57, 221, 219, 99, 177, 166, 239, 190, 191, 124, 227, 179, 194, 46, 26, 34, 78, 11, 47, 140, 126, 103, 21, 86, 86, 177, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}