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: c118cc9502641a2a77b0e66e73a07a50c7066299df73f667a1a0b034550461ab
Tx prefix hash: e8a2b8022602676d49dc77bd6e27dd5766a82ab093322a0ee4224ec66a373dc2
Tx public key: 0200ea36953105d966175d56a3a384cb697f90aa20c28af38b2fd98ef4e7b077
| Timestamp: 1779764629 | Timestamp [UTC]: 2026-05-26 03:03:49 | Age [y:d:h:m:s]: 00:013:22:32:08 |
| Block: 1954 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5932 | RingCT/type: yes/0 |
| Extra: 010200ea36953105d966175d56a3a384cb697f90aa20c28af38b2fd98ef4e7b07702090000000126697be300 | ||
1 output(s) for total of 35.053552159577 HMNY
| stealth address | amount | amount idx | tag |
| 00: 515b1e173b07b35777dbab48764936fe9a4ef63c4c629351e705f5b2e532cbcf | 35.053552159577 | 2218 of 0 | <d2> |
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": 2014,
"vin": [ {
"gen": {
"height": 1954
}
}
],
"vout": [ {
"amount": 35053552159577,
"target": {
"tagged_key": {
"key": "515b1e173b07b35777dbab48764936fe9a4ef63c4c629351e705f5b2e532cbcf",
"view_tag": "d2"
}
}
}
],
"extra": [ 1, 2, 0, 234, 54, 149, 49, 5, 217, 102, 23, 93, 86, 163, 163, 132, 203, 105, 127, 144, 170, 32, 194, 138, 243, 139, 47, 217, 142, 244, 231, 176, 119, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}