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: 3dfc5264b403b4c236fa63d61d9b2d62424939504c47f6fb1ace4baeab56c221
Tx prefix hash: d1b6e90bbb239c26e03de59175d9f59abbcf1dd36c0bf114be3dc7f7dddac8b6
Tx public key: 86781a7f0aa0723d03a79d354cd5e817885181e05d8f50c29577c0f2b873a84a
| Timestamp: 1780685822 | Timestamp [UTC]: 2026-06-05 18:57:02 | Age [y:d:h:m:s]: 00:003:06:38:55 |
| Block: 5401 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2485 | RingCT/type: yes/0 |
| Extra: 0186781a7f0aa0723d03a79d354cd5e817885181e05d8f50c29577c0f2b873a84a020900000001e49593ff00 | ||
1 output(s) for total of 34.823843730523 HMNY
| stealth address | amount | amount idx | tag |
| 00: 31c99dac5b90ef8ff35e30ab1810d4c4253e77373a9dbb4afede3a88326d2f8e | 34.823843730523 | 6838 of 0 | <e8> |
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": 5461,
"vin": [ {
"gen": {
"height": 5401
}
}
],
"vout": [ {
"amount": 34823843730523,
"target": {
"tagged_key": {
"key": "31c99dac5b90ef8ff35e30ab1810d4c4253e77373a9dbb4afede3a88326d2f8e",
"view_tag": "e8"
}
}
}
],
"extra": [ 1, 134, 120, 26, 127, 10, 160, 114, 61, 3, 167, 157, 53, 76, 213, 232, 23, 136, 81, 129, 224, 93, 143, 80, 194, 149, 119, 192, 242, 184, 115, 168, 74, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}