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: 092d573fce6d284447a0d9debd8a45e8118636b45eb3194865b858e91011bfec
Tx prefix hash: adfa6a139d443df21e2b42c328e8a00103b9b4f654566f343407a37b60f55a43
Tx public key: 59e51a591b55a239b2b933c3382c6c372e038dddc0e242e9a2ac43f4a7a5fa08
| Timestamp: 1780699382 | Timestamp [UTC]: 2026-06-05 22:43:02 | Age [y:d:h:m:s]: 00:003:03:57:34 |
| Block: 6033 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1863 | RingCT/type: yes/0 |
| Extra: 0159e51a591b55a239b2b933c3382c6c372e038dddc0e242e9a2ac43f4a7a5fa08020900000001e49593ff00 | ||
1 output(s) for total of 34.781890776388 HMNY
| stealth address | amount | amount idx | tag |
| 00: 34756e6273a7f3b3647896cbf5a49812d1a09002bdb4ad17c18189f928c2e248 | 34.781890776388 | 7502 of 0 | <e6> |
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": 6093,
"vin": [ {
"gen": {
"height": 6033
}
}
],
"vout": [ {
"amount": 34781890776388,
"target": {
"tagged_key": {
"key": "34756e6273a7f3b3647896cbf5a49812d1a09002bdb4ad17c18189f928c2e248",
"view_tag": "e6"
}
}
}
],
"extra": [ 1, 89, 229, 26, 89, 27, 85, 162, 57, 178, 185, 51, 195, 56, 44, 108, 55, 46, 3, 141, 221, 192, 226, 66, 233, 162, 172, 67, 244, 167, 165, 250, 8, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}