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: 4318d2cee240b2b42c92e303395a363a85622645b775f9a0f1c22c115c479868
Tx prefix hash: 45eec905db4c3529bdcdc8cb334e919eb1a2737ae1c503da92c7650cacd6f1d5
Tx public key: a9b03cd5e0b1cb37f8f3cced6703bf48a88e9deef11b419eb961fb9a3926216c
| Timestamp: 1779970540 | Timestamp [UTC]: 2026-05-28 12:15:40 | Age [y:d:h:m:s]: 00:011:14:34:08 |
| Block: 3841 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4059 | RingCT/type: yes/0 |
| Extra: 01a9b03cd5e0b1cb37f8f3cced6703bf48a88e9deef11b419eb961fb9a3926216c02090000000526697be300 | ||
1 output(s) for total of 34.927615225830 HMNY
| stealth address | amount | amount idx | tag |
| 00: f49725c4ce2f1fde81ba4c904daa4c60f9d86c039be447ec64be8eb3597068b1 | 34.927615225830 | 4687 of 0 | <47> |
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": 3901,
"vin": [ {
"gen": {
"height": 3841
}
}
],
"vout": [ {
"amount": 34927615225830,
"target": {
"tagged_key": {
"key": "f49725c4ce2f1fde81ba4c904daa4c60f9d86c039be447ec64be8eb3597068b1",
"view_tag": "47"
}
}
}
],
"extra": [ 1, 169, 176, 60, 213, 224, 177, 203, 55, 248, 243, 204, 237, 103, 3, 191, 72, 168, 142, 157, 238, 241, 27, 65, 158, 185, 97, 251, 154, 57, 38, 33, 108, 2, 9, 0, 0, 0, 5, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}