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: 16f1b4e756ee274f81fa47f901826f73abea8b6333025ee48cdb32e096a6dfa6
Tx prefix hash: 8e24429b91c76b3d1f4c68bf364af49be1d9ea70864a08bc5dbbb6773e18d147
Tx public key: 6fba8fdc7ceb0125cb8551f63269792681c6b0c66e624a189f97dceb02a4bb8b
| Timestamp: 1779891814 | Timestamp [UTC]: 2026-05-27 14:23:34 | Age [y:d:h:m:s]: 00:012:08:55:19 |
| Block: 3067 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4819 | RingCT/type: yes/0 |
| Extra: 016fba8fdc7ceb0125cb8551f63269792681c6b0c66e624a189f97dceb02a4bb8b02090000000226697be300 | ||
1 output(s) for total of 34.979216568588 HMNY
| stealth address | amount | amount idx | tag |
| 00: eea65db14c21956efbe632b9a78e73e8bd05d74180163bfb586b9ab1bd2b7504 | 34.979216568588 | 3651 of 0 | <a9> |
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": 3127,
"vin": [ {
"gen": {
"height": 3067
}
}
],
"vout": [ {
"amount": 34979216568588,
"target": {
"tagged_key": {
"key": "eea65db14c21956efbe632b9a78e73e8bd05d74180163bfb586b9ab1bd2b7504",
"view_tag": "a9"
}
}
}
],
"extra": [ 1, 111, 186, 143, 220, 124, 235, 1, 37, 203, 133, 81, 246, 50, 105, 121, 38, 129, 198, 176, 198, 110, 98, 74, 24, 159, 151, 220, 235, 2, 164, 187, 139, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}