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: 5f509f7231dcd09d584d8338ae1e47d7c4e8211e2a1f8d9bca46e0fbffb46d45
Tx prefix hash: 6c969dc713f3ff177cb58e2269c896067c78d8bcb7ce74612152cbd80b8d3e1d
Tx public key: d2e0c6508e2e6ec1fbbe9d51abae4bbdae67682256c369e1a2fbb335c491226e
| Timestamp: 1779715119 | Timestamp [UTC]: 2026-05-25 13:18:39 | Age [y:d:h:m:s]: 00:018:21:43:37 |
| Block: 1628 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7117 | RingCT/type: yes/0 |
| Extra: 01d2e0c6508e2e6ec1fbbe9d51abae4bbdae67682256c369e1a2fbb335c491226e020900000001ba6d17be00 | ||
1 output(s) for total of 35.075355104556 HMNY
| stealth address | amount | amount idx | tag |
| 00: 1d7cc33370e1a36ae851b9fc5cc425d82af47b733c0d9b792af86c0e3cc85001 | 35.075355104556 | 1786 of 0 | <30> |
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": 1688,
"vin": [ {
"gen": {
"height": 1628
}
}
],
"vout": [ {
"amount": 35075355104556,
"target": {
"tagged_key": {
"key": "1d7cc33370e1a36ae851b9fc5cc425d82af47b733c0d9b792af86c0e3cc85001",
"view_tag": "30"
}
}
}
],
"extra": [ 1, 210, 224, 198, 80, 142, 46, 110, 193, 251, 190, 157, 81, 171, 174, 75, 189, 174, 103, 104, 34, 86, 195, 105, 225, 162, 251, 179, 53, 196, 145, 34, 110, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}