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: eaf7995e50c84e1134f097f9e5c8a579dad166711bfb39e182bf5205e3f6e330
Tx prefix hash: 8e430cef17333237e248ceb92b93cd11c7fbcb7526753827c2e1a3eb37f6a748
Tx public key: 2390fad0e242847ed063cdd84457a790c9125b774b03cb07a814c0492213e197
| Timestamp: 1780083061 | Timestamp [UTC]: 2026-05-29 19:31:01 | Age [y:d:h:m:s]: 00:018:12:58:11 |
| Block: 4783 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3962 | RingCT/type: yes/0 |
| Extra: 012390fad0e242847ed063cdd84457a790c9125b774b03cb07a814c0492213e19702090000000326697be300 | ||
1 output(s) for total of 34.864916280126 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8a18ce9e59df703be64d600bfeeb629a8ffe19067b1a02c1af3d3887891f829a | 34.864916280126 | 6014 of 0 | <db> |
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": 4843,
"vin": [ {
"gen": {
"height": 4783
}
}
],
"vout": [ {
"amount": 34864916280126,
"target": {
"tagged_key": {
"key": "8a18ce9e59df703be64d600bfeeb629a8ffe19067b1a02c1af3d3887891f829a",
"view_tag": "db"
}
}
}
],
"extra": [ 1, 35, 144, 250, 208, 226, 66, 132, 126, 208, 99, 205, 216, 68, 87, 167, 144, 201, 18, 91, 119, 75, 3, 203, 7, 168, 20, 192, 73, 34, 19, 225, 151, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}