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: 3db2a4bf54d9495ec3ef2003fa061de882d31fdb952b6c9ce3c3579666efbe02
Tx prefix hash: 5f662bdd5d24f5b54ce3aa0089b3a5736e3cb59cd01fcf84f329dcf625447fae
Tx public key: e6b376a8932d203680c3ba0e55a7fe9695c3cc2be7f4d35275c1bb8886a4b664
| Timestamp: 1780765492 | Timestamp [UTC]: 2026-06-06 17:04:52 | Age [y:d:h:m:s]: 00:003:00:04:11 |
| Block: 6613 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2121 | RingCT/type: yes/0 |
| Extra: 01e6b376a8932d203680c3ba0e55a7fe9695c3cc2be7f4d35275c1bb8886a4b664020900000002e49593ff00 | ||
1 output(s) for total of 34.743434123951 HMNY
| stealth address | amount | amount idx | tag |
| 00: b739dc0d60638e55da3b7164b875aa18d2846b0f512349be3e2a646f859b7f8b | 34.743434123951 | 8149 of 0 | <58> |
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": 6673,
"vin": [ {
"gen": {
"height": 6613
}
}
],
"vout": [ {
"amount": 34743434123951,
"target": {
"tagged_key": {
"key": "b739dc0d60638e55da3b7164b875aa18d2846b0f512349be3e2a646f859b7f8b",
"view_tag": "58"
}
}
}
],
"extra": [ 1, 230, 179, 118, 168, 147, 45, 32, 54, 128, 195, 186, 14, 85, 167, 254, 150, 149, 195, 204, 43, 231, 244, 211, 82, 117, 193, 187, 136, 134, 164, 182, 100, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}