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: 052c699a8119cedf48005889cf011c704d427c18bcc8a5deee9598d5ce3bfa38
Tx prefix hash: 5f1b8a712dbc61fbc77b06a89b3021e31c0efe1f2703e3da590ab69b8e869d59
Tx public key: 88e51815d08bb699aefb9ffd6803894e4c281b3d22334fb9edcd5928b7db776b
| Timestamp: 1779721815 | Timestamp [UTC]: 2026-05-25 15:10:15 | Age [y:d:h:m:s]: 00:022:17:25:59 |
| Block: 1770 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6975 | RingCT/type: yes/0 |
| Extra: 0188e51815d08bb699aefb9ffd6803894e4c281b3d22334fb9edcd5928b7db776b020900000004ba6d17be00 | ||
1 output(s) for total of 35.065856449734 HMNY
| stealth address | amount | amount idx | tag |
| 00: f086cb2759123fe9858e6dfd866214f5dc2d421e5f4803a22e1f65f60b1a1501 | 35.065856449734 | 1955 of 0 | <a1> |
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": 1830,
"vin": [ {
"gen": {
"height": 1770
}
}
],
"vout": [ {
"amount": 35065856449734,
"target": {
"tagged_key": {
"key": "f086cb2759123fe9858e6dfd866214f5dc2d421e5f4803a22e1f65f60b1a1501",
"view_tag": "a1"
}
}
}
],
"extra": [ 1, 136, 229, 24, 21, 208, 139, 182, 153, 174, 251, 159, 253, 104, 3, 137, 78, 76, 40, 27, 61, 34, 51, 79, 185, 237, 205, 89, 40, 183, 219, 119, 107, 2, 9, 0, 0, 0, 4, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}