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: 78d2fc739d4b8e113e3d1f8c27abd28573ff8a4534bde4cd2433a6944d865dc8
Tx prefix hash: 2a501cf892d85165dd1c91a79489891fbdfd1021fee8614462d2929bba08a8ad
Tx public key: 2cad1d38a75ec213b8f0a5c724491d601b6c3cb85c07a5e665a039468111a20c
| Timestamp: 1780823150 | Timestamp [UTC]: 2026-06-07 09:05:50 | Age [y:d:h:m:s]: 00:001:16:30:07 |
| Block: 7213 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 673 | RingCT/type: yes/0 |
| Extra: 012cad1d38a75ec213b8f0a5c724491d601b6c3cb85c07a5e665a039468111a20c020900000002e49593ff00 | ||
1 output(s) for total of 34.703696123711 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5eb098af200ee8fae3297499c5dd5e145eb2ffdc96c6470d0be56bd375b98d8c | 34.703696123711 | 8883 of 0 | <f3> |
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": 7273,
"vin": [ {
"gen": {
"height": 7213
}
}
],
"vout": [ {
"amount": 34703696123711,
"target": {
"tagged_key": {
"key": "5eb098af200ee8fae3297499c5dd5e145eb2ffdc96c6470d0be56bd375b98d8c",
"view_tag": "f3"
}
}
}
],
"extra": [ 1, 44, 173, 29, 56, 167, 94, 194, 19, 184, 240, 165, 199, 36, 73, 29, 96, 27, 108, 60, 184, 92, 7, 165, 230, 101, 160, 57, 70, 129, 17, 162, 12, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}