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: 29d14aa27011206b94a2dac260f171831aee38b722a77d3ba746368782a23616
Tx prefix hash: 0d42e4f74fd8a10935479c6131efb516d1c82b5c63d0901d32d15551cca2219f
Tx public key: d2afdc58fe777e69fe19bf7e345ae58da581f63cc7a94cbefbb7151ce264c04c
| Timestamp: 1780819195 | Timestamp [UTC]: 2026-06-07 07:59:55 | Age [y:d:h:m:s]: 00:001:16:46:52 |
| Block: 7134 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 752 | RingCT/type: yes/0 |
| Extra: 01d2afdc58fe777e69fe19bf7e345ae58da581f63cc7a94cbefbb7151ce264c04c020900000001e49593ff00 | ||
1 output(s) for total of 34.726780494427 HMNY
| stealth address | amount | amount idx | tag |
| 00: 65e20a1c86a54f2620086bb24439421af4bac3515a31e66a36a1856cb6820eb9 | 34.726780494427 | 8790 of 0 | <44> |
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": 7194,
"vin": [ {
"gen": {
"height": 7134
}
}
],
"vout": [ {
"amount": 34726780494427,
"target": {
"tagged_key": {
"key": "65e20a1c86a54f2620086bb24439421af4bac3515a31e66a36a1856cb6820eb9",
"view_tag": "44"
}
}
}
],
"extra": [ 1, 210, 175, 220, 88, 254, 119, 126, 105, 254, 25, 191, 126, 52, 90, 229, 141, 165, 129, 246, 60, 199, 169, 76, 190, 251, 183, 21, 28, 226, 100, 192, 76, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}