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: 88a1bac0fc8c5af4deabbc6372f229b927ef85fdda8fe09353a3d2d8a1d62b8f
Tx prefix hash: 4155fd7cee9f318ef8f55440f56863213863c0a105f4242b5acccf57f0f38dc0
Tx public key: 22e1aff8b8605320cafbf38e04b3fcef9be2fcdd0d27dc8b1e044645964bfad6
| Timestamp: 1780897704 | Timestamp [UTC]: 2026-06-08 05:48:24 | Age [y:d:h:m:s]: 00:000:20:52:12 |
| Block: 7777 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 119 | RingCT/type: yes/0 |
| Extra: 0122e1aff8b8605320cafbf38e04b3fcef9be2fcdd0d27dc8b1e044645964bfad60209000000014a728a4c00 | ||
1 output(s) for total of 34.666383846259 HMNY
| stealth address | amount | amount idx | tag |
| 00: a57a29019f4333a9c6804bd11ee31aa226151f95bab923541673d71faba6747f | 34.666383846259 | 9637 of 0 | <4f> |
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": 7837,
"vin": [ {
"gen": {
"height": 7777
}
}
],
"vout": [ {
"amount": 34666383846259,
"target": {
"tagged_key": {
"key": "a57a29019f4333a9c6804bd11ee31aa226151f95bab923541673d71faba6747f",
"view_tag": "4f"
}
}
}
],
"extra": [ 1, 34, 225, 175, 248, 184, 96, 83, 32, 202, 251, 243, 142, 4, 179, 252, 239, 155, 226, 252, 221, 13, 39, 220, 139, 30, 4, 70, 69, 150, 75, 250, 214, 2, 9, 0, 0, 0, 1, 74, 114, 138, 76, 0
],
"rct_signatures": {
"type": 0
}
}