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: caee3f862dc98f6e33cf0c4fd49cee61e52a24383144380956c043b2d0817c2f
Tx prefix hash: ae68a18fbea4c1afa2a9f896ccf922a7a6fa5bd99692a09c3581a3fd9be29f4c
Tx public key: c7f534462b799dd40995d8fac5cd9e69ba9d289123d00a751861eccd5c74089b
| Timestamp: 1781026095 | Timestamp [UTC]: 2026-06-09 17:28:15 | Age [y:d:h:m:s]: 00:006:09:34:09 |
| Block: 8741 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4 | RingCT/type: yes/0 |
| Extra: 01c7f534462b799dd40995d8fac5cd9e69ba9d289123d00a751861eccd5c74089b020900000001e49593ff00 | ||
1 output(s) for total of 34.602701820871 HMNY
| stealth address | amount | amount idx | tag |
| 00: a81adb885fb975cf240433ef171ba3f86f1d8223fa63de52cefc9dc1c30ff97b | 34.602701820871 | 10813 of 0 | <7b> |
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": 8801,
"vin": [ {
"gen": {
"height": 8741
}
}
],
"vout": [ {
"amount": 34602701820871,
"target": {
"tagged_key": {
"key": "a81adb885fb975cf240433ef171ba3f86f1d8223fa63de52cefc9dc1c30ff97b",
"view_tag": "7b"
}
}
}
],
"extra": [ 1, 199, 245, 52, 70, 43, 121, 157, 212, 9, 149, 216, 250, 197, 205, 158, 105, 186, 157, 40, 145, 35, 208, 10, 117, 24, 97, 236, 205, 92, 116, 8, 155, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}