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: 6ce3c622c4df31553692297e24d6048c9a0d081301dd0cd15d78a9ea435c819d
Tx prefix hash: 35a07e4dcba3d8afd68a4bdf690c7900636a124a1bea77fffdf2c33f303fdd92
Tx public key: 17cba870f8a857acc66f74c14840e38a0f4a5447f65701dbcc7a72ba717db3bb
| Timestamp: 1779892769 | Timestamp [UTC]: 2026-05-27 14:39:29 | Age [y:d:h:m:s]: 00:012:10:07:18 |
| Block: 3074 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4812 | RingCT/type: yes/0 |
| Extra: 0117cba870f8a857acc66f74c14840e38a0f4a5447f65701dbcc7a72ba717db3bb02090000000226697be300 | ||
1 output(s) for total of 34.983761948334 HMNY
| stealth address | amount | amount idx | tag |
| 00: 08c52afa58ebca8e756e08ec834227a8bd76068335155b7f7aa15203586a8b65 | 34.983761948334 | 3660 of 0 | <23> |
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": 3134,
"vin": [ {
"gen": {
"height": 3074
}
}
],
"vout": [ {
"amount": 34983761948334,
"target": {
"tagged_key": {
"key": "08c52afa58ebca8e756e08ec834227a8bd76068335155b7f7aa15203586a8b65",
"view_tag": "23"
}
}
}
],
"extra": [ 1, 23, 203, 168, 112, 248, 168, 87, 172, 198, 111, 116, 193, 72, 64, 227, 138, 15, 74, 84, 71, 246, 87, 1, 219, 204, 122, 114, 186, 113, 125, 179, 187, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}