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: 1ab75696c46b4ff8c3fe0a3fd7fb9df233816e73bb426e82542eab99ae55c999
Tx prefix hash: e94f6f56e9820826f1a09df55b49c9862c29febfc7ea9641834d28faea6e0a52
Tx public key: fcd26622f412686549024b7240dc031a35a1f616a57985439d1ed2484317278e
| Timestamp: 1780778601 | Timestamp [UTC]: 2026-06-06 20:43:21 | Age [y:d:h:m:s]: 00:010:11:45:51 |
| Block: 6746 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1999 | RingCT/type: yes/0 |
| Extra: 01fcd26622f412686549024b7240dc031a35a1f616a57985439d1ed2484317278e020900000002e49593ff00 | ||
1 output(s) for total of 34.734621610432 HMNY
| stealth address | amount | amount idx | tag |
| 00: f270e9b2ebb59b4368ff3b1fd2514410eb907a6ee8a484587cc1b45b2520e8e4 | 34.734621610432 | 8324 of 0 | <df> |
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": 6806,
"vin": [ {
"gen": {
"height": 6746
}
}
],
"vout": [ {
"amount": 34734621610432,
"target": {
"tagged_key": {
"key": "f270e9b2ebb59b4368ff3b1fd2514410eb907a6ee8a484587cc1b45b2520e8e4",
"view_tag": "df"
}
}
}
],
"extra": [ 1, 252, 210, 102, 34, 244, 18, 104, 101, 73, 2, 75, 114, 64, 220, 3, 26, 53, 161, 246, 22, 165, 121, 133, 67, 157, 30, 210, 72, 67, 23, 39, 142, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}