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: 258d5209de53d1289e3e398bf6b690a6b7588160a2ecfadb5b1298e493521f90
Tx prefix hash: dbaa33c6288ce18fce41d7c6ebdb5555a210b09ce8b64c9734273ef3a832c92d
Tx public key: e51975b58cc75731c759d8becf1abaa5e62805bf061f756127874747e953f5a0
| Timestamp: 1780761446 | Timestamp [UTC]: 2026-06-06 15:57:26 | Age [y:d:h:m:s]: 00:002:10:52:22 |
| Block: 6572 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1348 | RingCT/type: yes/0 |
| Extra: 01e51975b58cc75731c759d8becf1abaa5e62805bf061f756127874747e953f5a0020900000002e49593ff00 | ||
1 output(s) for total of 34.746151214285 HMNY
| stealth address | amount | amount idx | tag |
| 00: c0d0929f5f049345211e0547de784f5f2760a7bee80f66f840cb1ba2058b9b0b | 34.746151214285 | 8094 of 0 | <b2> |
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": 6632,
"vin": [ {
"gen": {
"height": 6572
}
}
],
"vout": [ {
"amount": 34746151214285,
"target": {
"tagged_key": {
"key": "c0d0929f5f049345211e0547de784f5f2760a7bee80f66f840cb1ba2058b9b0b",
"view_tag": "b2"
}
}
}
],
"extra": [ 1, 229, 25, 117, 181, 140, 199, 87, 49, 199, 89, 216, 190, 207, 26, 186, 165, 230, 40, 5, 191, 6, 31, 117, 97, 39, 135, 71, 71, 233, 83, 245, 160, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}