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: 67d1234c8740ff66a965e43db6aa7039805a7488621cc43833f50d5f55d10b82
Tx prefix hash: f7f5bf2d8abb93a07a5ac5333a17d009ef6666afbe6ab27365d9f758812877b7
Tx public key: c5edbfee44127c0882a65782a9b6fdb7ccee25a3311bd7dcb438c83d4f2eeab9
| Timestamp: 1780857912 | Timestamp [UTC]: 2026-06-07 18:45:12 | Age [y:d:h:m:s]: 00:001:09:05:46 |
| Block: 7591 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 374 | RingCT/type: yes/0 |
| Extra: 01c5edbfee44127c0882a65782a9b6fdb7ccee25a3311bd7dcb438c83d4f2eeab9020900000004e49593ff00 | ||
1 output(s) for total of 34.678684523446 HMNY
| stealth address | amount | amount idx | tag |
| 00: 549e5f952a1a6d377abfd2ac719b0442872c2256b675e1cf1417cd5a34147a04 | 34.678684523446 | 9377 of 0 | <69> |
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": 7651,
"vin": [ {
"gen": {
"height": 7591
}
}
],
"vout": [ {
"amount": 34678684523446,
"target": {
"tagged_key": {
"key": "549e5f952a1a6d377abfd2ac719b0442872c2256b675e1cf1417cd5a34147a04",
"view_tag": "69"
}
}
}
],
"extra": [ 1, 197, 237, 191, 238, 68, 18, 124, 8, 130, 166, 87, 130, 169, 182, 253, 183, 204, 238, 37, 163, 49, 27, 215, 220, 180, 56, 200, 61, 79, 46, 234, 185, 2, 9, 0, 0, 0, 4, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}