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: 24d34d15bc66f7f99a9fffbdaede42826347d1a2b2e11f7835a0147cf74988b6
Tx prefix hash: 31fa80ab6c7c3118accdfed353189814a9bbf9db3f8aaeed12e4fe485e6a1a3d
Tx public key: dabe114c0ae6a1c7588b908e0879fb5ef1fd2568235789b030bb0e1c37e7e475
| Timestamp: 1780707438 | Timestamp [UTC]: 2026-06-06 00:57:18 | Age [y:d:h:m:s]: 00:003:01:43:18 |
| Block: 6128 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1769 | RingCT/type: yes/0 |
| Extra: 01dabe114c0ae6a1c7588b908e0879fb5ef1fd2568235789b030bb0e1c37e7e475020900000002e49593ff00 | ||
1 output(s) for total of 34.775588928114 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0f67f768e20ea5a8dbd60050cbbe207f8f82f8fd504e290cd3545dfd5828983d | 34.775588928114 | 7601 of 0 | <2f> |
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": 6188,
"vin": [ {
"gen": {
"height": 6128
}
}
],
"vout": [ {
"amount": 34775588928114,
"target": {
"tagged_key": {
"key": "0f67f768e20ea5a8dbd60050cbbe207f8f82f8fd504e290cd3545dfd5828983d",
"view_tag": "2f"
}
}
}
],
"extra": [ 1, 218, 190, 17, 76, 10, 230, 161, 199, 88, 139, 144, 142, 8, 121, 251, 94, 241, 253, 37, 104, 35, 87, 137, 176, 48, 187, 14, 28, 55, 231, 228, 117, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}