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: 44b020380989403018eae4ae6077f327f3272f061ad2fc6c022acc7fb1baf028
Tx prefix hash: b88fde3ac02259356e774c08435b69c6dd9f69da0d7afd379775b1ec6c1f298e
Tx public key: bfc9b22253f69dd2f1e7ccdda80c08c252c0b3d9f04a9a8f714d1e6b9ace4101
| Timestamp: 1780687848 | Timestamp [UTC]: 2026-06-05 19:30:48 | Age [y:d:h:m:s]: 00:003:05:15:59 |
| Block: 5502 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2384 | RingCT/type: yes/0 |
| Extra: 01bfc9b22253f69dd2f1e7ccdda80c08c252c0b3d9f04a9a8f714d1e6b9ace4101020900000002e49593ff00 | ||
1 output(s) for total of 34.817135827975 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0dfc88094bcb1087c82307dce00921b84b9fa684eeb62b313f34d6c8a6aab87a | 34.817135827975 | 6943 of 0 | <dd> |
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": 5562,
"vin": [ {
"gen": {
"height": 5502
}
}
],
"vout": [ {
"amount": 34817135827975,
"target": {
"tagged_key": {
"key": "0dfc88094bcb1087c82307dce00921b84b9fa684eeb62b313f34d6c8a6aab87a",
"view_tag": "dd"
}
}
}
],
"extra": [ 1, 191, 201, 178, 34, 83, 246, 157, 210, 241, 231, 204, 221, 168, 12, 8, 194, 82, 192, 179, 217, 240, 74, 154, 143, 113, 77, 30, 107, 154, 206, 65, 1, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}