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: d1b7b591e9dcba377aad330cc0cb735f2b57fe4916a40162035a9057b12677c1
Tx prefix hash: cd87a0ac0ac5a616f47bd25125c895b6c411232cc604794b9552a4457af0b569
Tx public key: 7a74a5b3182c30a9366483afd57d0751606f121f4e6e583560812d11e937aeac
| Timestamp: 1780816521 | Timestamp [UTC]: 2026-06-07 07:15:21 | Age [y:d:h:m:s]: 00:001:19:34:27 |
| Block: 7079 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 820 | RingCT/type: yes/0 |
| Extra: 017a74a5b3182c30a9366483afd57d0751606f121f4e6e583560812d11e937aeac020900000003e49593ff00 | ||
1 output(s) for total of 34.712567000099 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3d7a89b236f98048cbf75292959b03715945cf174d214dcfd3f45057438ca9f1 | 34.712567000099 | 8727 of 0 | <9c> |
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": 7139,
"vin": [ {
"gen": {
"height": 7079
}
}
],
"vout": [ {
"amount": 34712567000099,
"target": {
"tagged_key": {
"key": "3d7a89b236f98048cbf75292959b03715945cf174d214dcfd3f45057438ca9f1",
"view_tag": "9c"
}
}
}
],
"extra": [ 1, 122, 116, 165, 179, 24, 44, 48, 169, 54, 100, 131, 175, 213, 125, 7, 81, 96, 111, 18, 31, 78, 110, 88, 53, 96, 129, 45, 17, 233, 55, 174, 172, 2, 9, 0, 0, 0, 3, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}