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: b8cff71c87e56ae69035d9c47b1f4419c09db505ec5c7796d9b8357e997b9e17
Tx prefix hash: 1c001bd151c4f00206934cfa5e2bbca5e5b2ee5ba24cf2117c98852917096007
Tx public key: 096a80289a655e284d289c58a8e430b1f676238ad6a3fd333a638cacc1d0eae5
| Timestamp: 1779843704 | Timestamp [UTC]: 2026-05-27 01:01:44 | Age [y:d:h:m:s]: 00:013:00:34:13 |
| Block: 2427 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5459 | RingCT/type: yes/0 |
| Extra: 01096a80289a655e284d289c58a8e430b1f676238ad6a3fd333a638cacc1d0eae502090000000126697be300 | ||
1 output(s) for total of 35.021941920489 HMNY
| stealth address | amount | amount idx | tag |
| 00: 75229b6a09a5544fb906d64f7aac92d07c1b8ec28ba283ee029f6c8b550a39ca | 35.021941920489 | 2851 of 0 | <9b> |
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": 2487,
"vin": [ {
"gen": {
"height": 2427
}
}
],
"vout": [ {
"amount": 35021941920489,
"target": {
"tagged_key": {
"key": "75229b6a09a5544fb906d64f7aac92d07c1b8ec28ba283ee029f6c8b550a39ca",
"view_tag": "9b"
}
}
}
],
"extra": [ 1, 9, 106, 128, 40, 154, 101, 94, 40, 77, 40, 156, 88, 168, 228, 48, 177, 246, 118, 35, 138, 214, 163, 253, 51, 58, 99, 140, 172, 193, 208, 234, 229, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}