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: bc2952469cab0dc62637d853d1317c4e9dfb026412ab727415384e508c9e62ec
Tx prefix hash: 9cb922d1fed1b1fe681171959fd3df50742cdb94d7e477ded8a9d399bc679344
Tx public key: e1245f95911c34312221f7ac1a01c72feadfcde584c98d9410a3737b9c8d925c
| Timestamp: 1780810377 | Timestamp [UTC]: 2026-06-07 05:32:57 | Age [y:d:h:m:s]: 00:002:11:36:06 |
| Block: 7015 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1718 | RingCT/type: yes/0 |
| Extra: 01e1245f95911c34312221f7ac1a01c72feadfcde584c98d9410a3737b9c8d925c020900000001e49593ff00 | ||
1 output(s) for total of 34.716804636681 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4a6fc04361cb65a0b117a0b3c1dbd857f39b1dc8ddd5d7ba4b0ebbc8fc96397d | 34.716804636681 | 8651 of 0 | <55> |
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": 7075,
"vin": [ {
"gen": {
"height": 7015
}
}
],
"vout": [ {
"amount": 34716804636681,
"target": {
"tagged_key": {
"key": "4a6fc04361cb65a0b117a0b3c1dbd857f39b1dc8ddd5d7ba4b0ebbc8fc96397d",
"view_tag": "55"
}
}
}
],
"extra": [ 1, 225, 36, 95, 149, 145, 28, 52, 49, 34, 33, 247, 172, 26, 1, 199, 47, 234, 223, 205, 229, 132, 201, 141, 148, 16, 163, 115, 123, 156, 141, 146, 92, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}