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: 8de8f8c6fd2cf3cce35095b6d30b053adb6e0d8930b143f5c912e453814d6469
Tx prefix hash: c5c2d115f08fc00841c4c4c3cd85f5ef3badb5c278aea1d08ec89e282146bc4a
Tx public key: a58ebe8958a47900fcc8a8659c46aa1ee91b0113f6aec58cf0d29294575b0818
| Timestamp: 1779634688 | Timestamp [UTC]: 2026-05-24 14:58:08 | Age [y:d:h:m:s]: 00:015:10:37:49 |
| Block: 1042 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6844 | RingCT/type: yes/0 |
| Extra: 01a58ebe8958a47900fcc8a8659c46aa1ee91b0113f6aec58cf0d29294575b0818020900000001ba6d17be00 | ||
1 output(s) for total of 35.114581004733 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5db731a58b5ad64773f59f7f56ad765452c4f603eeb2e7360440ba40940ea0a3 | 35.114581004733 | 1180 of 0 | <4a> |
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": 1102,
"vin": [ {
"gen": {
"height": 1042
}
}
],
"vout": [ {
"amount": 35114581004733,
"target": {
"tagged_key": {
"key": "5db731a58b5ad64773f59f7f56ad765452c4f603eeb2e7360440ba40940ea0a3",
"view_tag": "4a"
}
}
}
],
"extra": [ 1, 165, 142, 190, 137, 88, 164, 121, 0, 252, 200, 168, 101, 156, 70, 170, 30, 233, 27, 1, 19, 246, 174, 197, 140, 240, 210, 146, 148, 87, 91, 8, 24, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}