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: eabee1d5bdae490770b26f145c0d0c881450075ef630304a7a746555e1515d70
Tx prefix hash: 4f393e5054a55e07234f7eef7afedec144e07c9c0f6ec55bc3e4b9f725a3a22c
Tx public key: 464a38c5858381e110265cf45674aaa32ec6eb4452683a54ca56853657d7294c
| Timestamp: 1780689662 | Timestamp [UTC]: 2026-06-05 20:01:02 | Age [y:d:h:m:s]: 00:003:03:17:51 |
| Block: 5612 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2274 | RingCT/type: yes/0 |
| Extra: 01464a38c5858381e110265cf45674aaa32ec6eb4452683a54ca56853657d7294c020900000001e49593ff00 | ||
1 output(s) for total of 34.809831661467 HMNY
| stealth address | amount | amount idx | tag |
| 00: e54d2880d310de6b08ecaa8e00608938b8375caff067277d658bd559ebbbb382 | 34.809831661467 | 7059 of 0 | <80> |
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": 5672,
"vin": [ {
"gen": {
"height": 5612
}
}
],
"vout": [ {
"amount": 34809831661467,
"target": {
"tagged_key": {
"key": "e54d2880d310de6b08ecaa8e00608938b8375caff067277d658bd559ebbbb382",
"view_tag": "80"
}
}
}
],
"extra": [ 1, 70, 74, 56, 197, 133, 131, 129, 225, 16, 38, 92, 244, 86, 116, 170, 163, 46, 198, 235, 68, 82, 104, 58, 84, 202, 86, 133, 54, 87, 215, 41, 76, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}