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: d0b351eece807b56a8c68bdac9d229d2a754c285d0c5f9f2631d9c61244567e4
Tx prefix hash: 98733019eda9a49b23de1650b697746372c9159ad40afcdab02c5ce5705a6ed1
Tx public key: 23c67255f945c0e6bd6a6ec0abf035cc9e6c7bcb5a5f277b06b0ac524a0e2db0
| Timestamp: 1780038859 | Timestamp [UTC]: 2026-05-29 07:14:19 | Age [y:d:h:m:s]: 00:010:19:26:17 |
| Block: 4263 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3634 | RingCT/type: yes/0 |
| Extra: 0123c67255f945c0e6bd6a6ec0abf035cc9e6c7bcb5a5f277b06b0ac524a0e2db002090000000326697be300 | ||
1 output(s) for total of 34.899513233489 HMNY
| stealth address | amount | amount idx | tag |
| 00: 27bde845f32883ac74cad6a8befa9ba02db821f300f0890db2b6466bc81287a3 | 34.899513233489 | 5324 of 0 | <1c> |
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": 4323,
"vin": [ {
"gen": {
"height": 4263
}
}
],
"vout": [ {
"amount": 34899513233489,
"target": {
"tagged_key": {
"key": "27bde845f32883ac74cad6a8befa9ba02db821f300f0890db2b6466bc81287a3",
"view_tag": "1c"
}
}
}
],
"extra": [ 1, 35, 198, 114, 85, 249, 69, 192, 230, 189, 106, 110, 192, 171, 240, 53, 204, 158, 108, 123, 203, 90, 95, 39, 123, 6, 176, 172, 82, 74, 14, 45, 176, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}