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: fbea565f4b37a240b9ee49e3f1241b0b8f9a95e8d85f60bfa3c1441e752b394e
Tx prefix hash: f3c026b875ed759df0c4caebc5591a9e8346f88c1ca97acbd14dab70c35ca796
Tx public key: 9e37bd95ce80e368a442c4d0614147365d24172310e394734c2178a02994a627
| Timestamp: 1779784587 | Timestamp [UTC]: 2026-05-26 08:36:27 | Age [y:d:h:m:s]: 00:013:16:10:20 |
| Block: 2148 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5738 | RingCT/type: yes/0 |
| Extra: 019e37bd95ce80e368a442c4d0614147365d24172310e394734c2178a02994a62702090000000226697be300 | ||
1 output(s) for total of 35.040583833775 HMNY
| stealth address | amount | amount idx | tag |
| 00: 92fc8b736eb8f3e0a89cd6a4df8d38f5ac198cc918a683332a1939d600d62d1c | 35.040583833775 | 2478 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": 2208,
"vin": [ {
"gen": {
"height": 2148
}
}
],
"vout": [ {
"amount": 35040583833775,
"target": {
"tagged_key": {
"key": "92fc8b736eb8f3e0a89cd6a4df8d38f5ac198cc918a683332a1939d600d62d1c",
"view_tag": "e5"
}
}
}
],
"extra": [ 1, 158, 55, 189, 149, 206, 128, 227, 104, 164, 66, 196, 208, 97, 65, 71, 54, 93, 36, 23, 35, 16, 227, 148, 115, 76, 33, 120, 160, 41, 148, 166, 39, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}