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: eb2eac1bbf9ccc417dcbc040adecb309ef91215def8dd7b91916de06965e1153
Tx prefix hash: 42e02c2da6013cc8fde4f50a0b48e18a6734be062cf6c252fda33c8e25892a73
Tx public key: 4c6c279eee793c72322766e2944dfbd0908352d2867e5c30b7d9f0b5be89495f
| Timestamp: 1779807439 | Timestamp [UTC]: 2026-05-26 14:57:19 | Age [y:d:h:m:s]: 00:013:11:43:17 |
| Block: 2364 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5532 | RingCT/type: yes/0 |
| Extra: 014c6c279eee793c72322766e2944dfbd0908352d2867e5c30b7d9f0b5be89495f02090000000126697be300 | ||
1 output(s) for total of 35.026150517698 HMNY
| stealth address | amount | amount idx | tag |
| 00: 64ca029d21d6e089b0d70fe76f2478e21ed73bdeef1e8a5ebd7a67e6f148ad46 | 35.026150517698 | 2770 of 0 | <ef> |
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": 2424,
"vin": [ {
"gen": {
"height": 2364
}
}
],
"vout": [ {
"amount": 35026150517698,
"target": {
"tagged_key": {
"key": "64ca029d21d6e089b0d70fe76f2478e21ed73bdeef1e8a5ebd7a67e6f148ad46",
"view_tag": "ef"
}
}
}
],
"extra": [ 1, 76, 108, 39, 158, 238, 121, 60, 114, 50, 39, 102, 226, 148, 77, 251, 208, 144, 131, 82, 210, 134, 126, 92, 48, 183, 217, 240, 181, 190, 137, 73, 95, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}