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: 2afc29737d60a55a46721e789165e5460ab438875d323e9e0f12544fd3c16d98
Tx prefix hash: ca14c569f434aa40efe3305cabd545e8c02981802df7050012f41711e3cb5bbf
Tx public key: 57d1192c9ef6c956ed4095234f25fddb36b6a2e55011805909dee41253952eef
| Timestamp: 1779716094 | Timestamp [UTC]: 2026-05-25 13:34:54 | Age [y:d:h:m:s]: 00:014:09:43:59 |
| Block: 1649 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6237 | RingCT/type: yes/0 |
| Extra: 0157d1192c9ef6c956ed4095234f25fddb36b6a2e55011805909dee41253952eef020900000001ba6d17be00 | ||
1 output(s) for total of 35.073950211810 HMNY
| stealth address | amount | amount idx | tag |
| 00: 79dca4b49bd6bf53d695e08059a5729055ae4936948f8de5275709f0cc5123c3 | 35.073950211810 | 1811 of 0 | <06> |
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": 1709,
"vin": [ {
"gen": {
"height": 1649
}
}
],
"vout": [ {
"amount": 35073950211810,
"target": {
"tagged_key": {
"key": "79dca4b49bd6bf53d695e08059a5729055ae4936948f8de5275709f0cc5123c3",
"view_tag": "06"
}
}
}
],
"extra": [ 1, 87, 209, 25, 44, 158, 246, 201, 86, 237, 64, 149, 35, 79, 37, 253, 219, 54, 182, 162, 229, 80, 17, 128, 89, 9, 222, 228, 18, 83, 149, 46, 239, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}