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: 56e2d5fb9d6289f305ed2e99d8427c6916bdf82c37210930fcc321b9693f71d1
Tx prefix hash: b85f92a89a53819929f707b284e33e4fc65d7a51cc81459db1cc1ace93488b72
Tx public key: 2e8044f77622fe6b0067bd0eeb36ba68cb06d417be9e10e1456ecab02ee35259
| Timestamp: 1779740285 | Timestamp [UTC]: 2026-05-25 20:18:05 | Age [y:d:h:m:s]: 00:014:05:17:52 |
| Block: 1934 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5952 | RingCT/type: yes/0 |
| Extra: 012e8044f77622fe6b0067bd0eeb36ba68cb06d417be9e10e1456ecab02ee3525902090000000326697be300 | ||
1 output(s) for total of 35.054889373253 HMNY
| stealth address | amount | amount idx | tag |
| 00: b882f4cc08268d442f9840fa17c033deebbd3748c4c02b8337e96c1705e83f97 | 35.054889373253 | 2182 of 0 | <c5> |
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": 1994,
"vin": [ {
"gen": {
"height": 1934
}
}
],
"vout": [ {
"amount": 35054889373253,
"target": {
"tagged_key": {
"key": "b882f4cc08268d442f9840fa17c033deebbd3748c4c02b8337e96c1705e83f97",
"view_tag": "c5"
}
}
}
],
"extra": [ 1, 46, 128, 68, 247, 118, 34, 254, 107, 0, 103, 189, 14, 235, 54, 186, 104, 203, 6, 212, 23, 190, 158, 16, 225, 69, 110, 202, 176, 46, 227, 82, 89, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}