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: d45ede96595bfc7d3f15171db7676cc5915ec8bdfd0ad4f8a55554e4623d4acd
Tx prefix hash: 43ea48639804c7706939b219f0d4de87ce7793b347d35544de7cb372c1b68538
Tx public key: 788bc69ae58b5f5787c69131287652faf1ccc89ac68ba1f8ed1ded99cbc1b6c8
| Timestamp: 1779435260 | Timestamp [UTC]: 2026-05-22 07:34:20 | Age [y:d:h:m:s]: 00:022:03:26:37 |
| Block: 117 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0918 kB |
| Tx version: 2 | No of confirmations: 8628 | RingCT/type: yes/0 |
| Extra: 01788bc69ae58b5f5787c69131287652faf1ccc89ac68ba1f8ed1ded99cbc1b6c8020900000002a662ed0300 | ||
1 output(s) for total of 35.176588314419 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5d61091d68b3aa2e0dafbfbbe02f03860643230ebf6b050f5b5988aedb4e25fc | 35.176588314419 | 113 of 0 | <b6> |
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": 177,
"vin": [ {
"gen": {
"height": 117
}
}
],
"vout": [ {
"amount": 35176588314419,
"target": {
"tagged_key": {
"key": "5d61091d68b3aa2e0dafbfbbe02f03860643230ebf6b050f5b5988aedb4e25fc",
"view_tag": "b6"
}
}
}
],
"extra": [ 1, 120, 139, 198, 154, 229, 139, 95, 87, 135, 198, 145, 49, 40, 118, 82, 250, 241, 204, 200, 154, 198, 139, 161, 248, 237, 29, 237, 153, 203, 193, 182, 200, 2, 9, 0, 0, 0, 2, 166, 98, 237, 3, 0
],
"rct_signatures": {
"type": 0
}
}