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: 4d3a2ba8c41a68fe28f9bee47c77120a5bed237a2be28fbcf6f2f7cf2afb30f9
Tx prefix hash: 4b0cae84da1140c0187f44d692bb7a025d124712fa93cf0c6106bb725afbb13e
Tx public key: ada09859fb87e9b93e75e81d4e0422616aacb220125ec7e7c43922bca7ad6d05
| Timestamp: 1780694186 | Timestamp [UTC]: 2026-06-05 21:16:26 | Age [y:d:h:m:s]: 00:003:19:52:37 |
| Block: 5920 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2813 | RingCT/type: yes/0 |
| Extra: 01ada09859fb87e9b93e75e81d4e0422616aacb220125ec7e7c43922bca7ad6d05020900000001e49593ff00 | ||
1 output(s) for total of 34.789388146140 HMNY
| stealth address | amount | amount idx | tag |
| 00: 05f57a3086b85d86904e552be30689d6a784ad222787083c2788c92bd501df80 | 34.789388146140 | 7381 of 0 | <d1> |
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": 5980,
"vin": [ {
"gen": {
"height": 5920
}
}
],
"vout": [ {
"amount": 34789388146140,
"target": {
"tagged_key": {
"key": "05f57a3086b85d86904e552be30689d6a784ad222787083c2788c92bd501df80",
"view_tag": "d1"
}
}
}
],
"extra": [ 1, 173, 160, 152, 89, 251, 135, 233, 185, 62, 117, 232, 29, 78, 4, 34, 97, 106, 172, 178, 32, 18, 94, 199, 231, 196, 57, 34, 188, 167, 173, 109, 5, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}