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: 82f5beba9b6cd26aeab8dfc5976a99715d61e1ad051647bfe86b11f123be426c
Tx prefix hash: e34645371456cd96f150a0e66f7e2e9ace9a4ec756f60ed8f9f143083b9324dc
Tx public key: f748f02cbed917179e3d9683f0c49a083031566064dd2b8c52d7a0f198955b14
| Timestamp: 1780997787 | Timestamp [UTC]: 2026-06-09 09:36:27 | Age [y:d:h:m:s]: 00:000:06:23:17 |
| Block: 8381 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 310 | RingCT/type: yes/0 |
| Extra: 01f748f02cbed917179e3d9683f0c49a083031566064dd2b8c52d7a0f198955b14020900000001e49593ff00 | ||
1 output(s) for total of 34.626469792453 HMNY
| stealth address | amount | amount idx | tag |
| 00: aa6cc17a90cfdb7d3ff9cfd23631bd1941a0eb9824a07e080dc7ec40e51a2ea7 | 34.626469792453 | 10361 of 0 | <33> |
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": 8441,
"vin": [ {
"gen": {
"height": 8381
}
}
],
"vout": [ {
"amount": 34626469792453,
"target": {
"tagged_key": {
"key": "aa6cc17a90cfdb7d3ff9cfd23631bd1941a0eb9824a07e080dc7ec40e51a2ea7",
"view_tag": "33"
}
}
}
],
"extra": [ 1, 247, 72, 240, 44, 190, 217, 23, 23, 158, 61, 150, 131, 240, 196, 154, 8, 48, 49, 86, 96, 100, 221, 43, 140, 82, 215, 160, 241, 152, 149, 91, 20, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}