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: ee5ddb39a10435a2a25b97a8e33409649ec2f37b206758ef31e28ef1bc7ef368
Tx prefix hash: 529c5f208a0692d14b5f36d38d2369b057b81641ec23eda99a0df77aec1363bd
Tx public key: 757f0482548454abd4e621a989f0ce5886add712d66ece3659f15483db5ba393
| Timestamp: 1780810557 | Timestamp [UTC]: 2026-06-07 05:35:57 | Age [y:d:h:m:s]: 00:001:20:00:00 |
| Block: 7018 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 868 | RingCT/type: yes/0 |
| Extra: 01757f0482548454abd4e621a989f0ce5886add712d66ece3659f15483db5ba393020900000002e49593ff00 | ||
1 output(s) for total of 34.716605985910 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7109a6a7c9f9f05ad01d697c2471ee93f3844343662ee957731d39b7c18aa424 | 34.716605985910 | 8654 of 0 | <e5> |
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": 7078,
"vin": [ {
"gen": {
"height": 7018
}
}
],
"vout": [ {
"amount": 34716605985910,
"target": {
"tagged_key": {
"key": "7109a6a7c9f9f05ad01d697c2471ee93f3844343662ee957731d39b7c18aa424",
"view_tag": "e5"
}
}
}
],
"extra": [ 1, 117, 127, 4, 130, 84, 132, 84, 171, 212, 230, 33, 169, 137, 240, 206, 88, 134, 173, 215, 18, 214, 110, 206, 54, 89, 241, 84, 131, 219, 91, 163, 147, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}