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: 19035dc04f1332579c4ed2cea5b82c740de1958270c8c8f5bd76d83040794d44
Tx prefix hash: 2a540e5f089a63321334e9dba9b779241a88995ab5371b75a9669543c1bf1f1d
Tx public key: 01fb9a1cf0564eb37438f45cbe2cf3fc5c2a7a2ed2880a710786c99aed709295
| Timestamp: 1780861302 | Timestamp [UTC]: 2026-06-07 19:41:42 | Age [y:d:h:m:s]: 00:009:12:47:30 |
| Block: 7621 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1124 | RingCT/type: yes/0 |
| Extra: 0101fb9a1cf0564eb37438f45cbe2cf3fc5c2a7a2ed2880a710786c99aed709295020900000003e49593ff00 | ||
1 output(s) for total of 34.676700248079 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0792be18d4e1fa965879ee6de888485801b371a271fad7549f77e4dac8912b42 | 34.676700248079 | 9419 of 0 | <b4> |
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": 7681,
"vin": [ {
"gen": {
"height": 7621
}
}
],
"vout": [ {
"amount": 34676700248079,
"target": {
"tagged_key": {
"key": "0792be18d4e1fa965879ee6de888485801b371a271fad7549f77e4dac8912b42",
"view_tag": "b4"
}
}
}
],
"extra": [ 1, 1, 251, 154, 28, 240, 86, 78, 179, 116, 56, 244, 92, 190, 44, 243, 252, 92, 42, 122, 46, 210, 136, 10, 113, 7, 134, 201, 154, 237, 112, 146, 149, 2, 9, 0, 0, 0, 3, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}