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: c51f282e59dd24602b9a00b1d2e8c118d0e7a7504e5562ec9040cdead755a271
Tx prefix hash: c568af6add17df6fe440307e80a649e820d4b95cfaefddf234a31419f15af865
Tx public key: aa0a1e106b402c0e057fb326b1c346a21e208022a2024418ad71a4c5a8f9c1e1
| Timestamp: 1779854090 | Timestamp [UTC]: 2026-05-27 03:54:50 | Age [y:d:h:m:s]: 00:012:21:41:07 |
| Block: 2587 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5299 | RingCT/type: yes/0 |
| Extra: 01aa0a1e106b402c0e057fb326b1c346a21e208022a2024418ad71a4c5a8f9c1e102090000000126697be300 | ||
1 output(s) for total of 35.011255692483 HMNY
| stealth address | amount | amount idx | tag |
| 00: b681de29e756e40606e02d1942c807ccc0d02f2076130e676411058cdbddec4c | 35.011255692483 | 3045 of 0 | <70> |
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": 2647,
"vin": [ {
"gen": {
"height": 2587
}
}
],
"vout": [ {
"amount": 35011255692483,
"target": {
"tagged_key": {
"key": "b681de29e756e40606e02d1942c807ccc0d02f2076130e676411058cdbddec4c",
"view_tag": "70"
}
}
}
],
"extra": [ 1, 170, 10, 30, 16, 107, 64, 44, 14, 5, 127, 179, 38, 177, 195, 70, 162, 30, 32, 128, 34, 162, 2, 68, 24, 173, 113, 164, 197, 168, 249, 193, 225, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}