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: 92f83ee1d2115c232ca10ea89e722ed4c54a9afed0fc6df3e136c22ea5cdbea1
Tx prefix hash: 9f62fdcabb00f7d24fcdec289ce555285305fc897cbff79cff89896d9ed7d3aa
Tx public key: c5ccad4c5bada08c13c3325c513e304e3c81d2cb2f9ea283d656aa9b2e1a1b97
| Timestamp: 1779951113 | Timestamp [UTC]: 2026-05-28 06:51:53 | Age [y:d:h:m:s]: 00:020:01:09:52 |
| Block: 3625 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5120 | RingCT/type: yes/0 |
| Extra: 01c5ccad4c5bada08c13c3325c513e304e3c81d2cb2f9ea283d656aa9b2e1a1b9702090000000226697be300 | ||
1 output(s) for total of 34.942007938216 HMNY
| stealth address | amount | amount idx | tag |
| 00: f7807fa5791a214ce32a0df09dea48c1d31a90ea99a146cb07a2a4a77b3349ab | 34.942007938216 | 4378 of 0 | <d2> |
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": 3685,
"vin": [ {
"gen": {
"height": 3625
}
}
],
"vout": [ {
"amount": 34942007938216,
"target": {
"tagged_key": {
"key": "f7807fa5791a214ce32a0df09dea48c1d31a90ea99a146cb07a2a4a77b3349ab",
"view_tag": "d2"
}
}
}
],
"extra": [ 1, 197, 204, 173, 76, 91, 173, 160, 140, 19, 195, 50, 92, 81, 62, 48, 78, 60, 129, 210, 203, 47, 158, 162, 131, 214, 86, 170, 155, 46, 26, 27, 151, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}