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: 3c2b14540e97fe33f2a1eaafa6f91b0f13e74a974b5f879ad997d8cd5d584530
Tx prefix hash: e1291b58f35c155cf54b154d89414f04f12e2e06dfce372ab9b1fbbf76effa3d
Tx public key: c54885fa7abfb90e430007a882445a95e797fcf2e37b2a7bf86c11c9e3e5f54c
| Timestamp: 1780975023 | Timestamp [UTC]: 2026-06-09 03:17:03 | Age [y:d:h:m:s]: 00:000:08:17:31 |
| Block: 7923 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 623 | RingCT/type: yes/0 |
| Extra: 01c54885fa7abfb90e430007a882445a95e797fcf2e37b2a7bf86c11c9e3e5f54c020900000002e49593ff00 | ||
1 output(s) for total of 34.656731532614 HMNY
| stealth address | amount | amount idx | tag |
| 00: abfe9872f7d43330190fc83c9646435c0e8daad0f0972777331f1d31b5a19e61 | 34.656731532614 | 9825 of 0 | <63> |
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": 7983,
"vin": [ {
"gen": {
"height": 7923
}
}
],
"vout": [ {
"amount": 34656731532614,
"target": {
"tagged_key": {
"key": "abfe9872f7d43330190fc83c9646435c0e8daad0f0972777331f1d31b5a19e61",
"view_tag": "63"
}
}
}
],
"extra": [ 1, 197, 72, 133, 250, 122, 191, 185, 14, 67, 0, 7, 168, 130, 68, 90, 149, 231, 151, 252, 242, 227, 123, 42, 123, 248, 108, 17, 201, 227, 229, 245, 76, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}