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: a6dfebdedb69fe525db63bcbea9ff7ef0a2ccd09dfad62d408356e7836003d0a
Tx prefix hash: 4b00acde618c29d7982fe804caee19273f7c83ef93fae7a7e6a081dac0379e48
Tx public key: 8316dc4d8c7427a8cdc8ade4e9e9eddd315b4825542dc25f5c7a32c88e09e122
| Timestamp: 1780002092 | Timestamp [UTC]: 2026-05-28 21:01:32 | Age [y:d:h:m:s]: 00:015:14:00:44 |
| Block: 4061 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4684 | RingCT/type: yes/0 |
| Extra: 018316dc4d8c7427a8cdc8ade4e9e9eddd315b4825542dc25f5c7a32c88e09e12202090000001226697be300 | ||
1 output(s) for total of 34.912962075811 HMNY
| stealth address | amount | amount idx | tag |
| 00: 149716aaf7c45eb792a6d505febda323ec730bf5be0460d45e77fede47dbbcdc | 34.912962075811 | 5035 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": 4121,
"vin": [ {
"gen": {
"height": 4061
}
}
],
"vout": [ {
"amount": 34912962075811,
"target": {
"tagged_key": {
"key": "149716aaf7c45eb792a6d505febda323ec730bf5be0460d45e77fede47dbbcdc",
"view_tag": "ed"
}
}
}
],
"extra": [ 1, 131, 22, 220, 77, 140, 116, 39, 168, 205, 200, 173, 228, 233, 233, 237, 221, 49, 91, 72, 37, 84, 45, 194, 95, 92, 122, 50, 200, 142, 9, 225, 34, 2, 9, 0, 0, 0, 18, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}