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: 1d605bffc0af9bb62e351d2fd5ef67699b4acbbae4cec738e657fb898af82cb9
Tx prefix hash: c0e53dae65d04991633e455f5b1e90376c6b27f4d0e9cbc8d32a174b4daf9a57
Tx public key: a1e424d75ef5c3e11938ff0cef2ac26c82ca4f48f74ac439d83da691016bf604
| Timestamp: 1780988658 | Timestamp [UTC]: 2026-06-09 07:04:18 | Age [y:d:h:m:s]: 00:008:04:31:47 |
| Block: 8187 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 558 | RingCT/type: yes/0 |
| Extra: 01a1e424d75ef5c3e11938ff0cef2ac26c82ca4f48f74ac439d83da691016bf604020900000001e49593ff00 | ||
1 output(s) for total of 34.639284856944 HMNY
| stealth address | amount | amount idx | tag |
| 00: af080a8e7adaf15f89a3b10660a423a5924c2ee27eeb355940e217fb5faf2a0f | 34.639284856944 | 10137 of 0 | <43> |
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": 8247,
"vin": [ {
"gen": {
"height": 8187
}
}
],
"vout": [ {
"amount": 34639284856944,
"target": {
"tagged_key": {
"key": "af080a8e7adaf15f89a3b10660a423a5924c2ee27eeb355940e217fb5faf2a0f",
"view_tag": "43"
}
}
}
],
"extra": [ 1, 161, 228, 36, 215, 94, 245, 195, 225, 25, 56, 255, 12, 239, 42, 194, 108, 130, 202, 79, 72, 247, 74, 196, 57, 216, 61, 166, 145, 1, 107, 246, 4, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}