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: 9767a84119cae49917b2347c0d9c1a2bf6822290c20832aec6af80c0dd575db9
Tx prefix hash: 2a61b1f2364d5374f57abfc9073f3a1a2ac8c350cd5e393dc3f59e9e4f73ec49
Tx public key: 34728438f97e276867e410c585161f7ce4cb6fad19e3fda0e2faeb731413c899
| Timestamp: 1780323489 | Timestamp [UTC]: 2026-06-01 14:18:09 | Age [y:d:h:m:s]: 00:007:13:32:49 |
| Block: 5153 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2813 | RingCT/type: yes/0 |
| Extra: 0134728438f97e276867e410c585161f7ce4cb6fad19e3fda0e2faeb731413c89902090000000126697be300 | ||
1 output(s) for total of 34.840320103036 HMNY
| stealth address | amount | amount idx | tag |
| 00: 1ea7095bced9957bc28d5ae901cb35bba53e46b9fe3280cc2230033f7f0cad90 | 34.840320103036 | 6528 of 0 | <70> |
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": 5213,
"vin": [ {
"gen": {
"height": 5153
}
}
],
"vout": [ {
"amount": 34840320103036,
"target": {
"tagged_key": {
"key": "1ea7095bced9957bc28d5ae901cb35bba53e46b9fe3280cc2230033f7f0cad90",
"view_tag": "70"
}
}
}
],
"extra": [ 1, 52, 114, 132, 56, 249, 126, 39, 104, 103, 228, 16, 197, 133, 22, 31, 124, 228, 203, 111, 173, 25, 227, 253, 160, 226, 250, 235, 115, 20, 19, 200, 153, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}