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: 8d6022a5de1a0fac1d47e0a9a7e176a806975a0f2b5c501e477957cd983c9f3c
Tx prefix hash: ad0d18939af3b1d07c14128b24c93e5b2376990874ec2eba4de60875e003a6fe
Tx public key: e8beecb840228620ec14b5b77820a911f6e6ca59c72b8f1f1b5ba0b15aa26db9
| Timestamp: 1779770286 | Timestamp [UTC]: 2026-05-26 04:38:06 | Age [y:d:h:m:s]: 00:013:22:11:42 |
| Block: 2002 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5918 | RingCT/type: yes/0 |
| Extra: 01e8beecb840228620ec14b5b77820a911f6e6ca59c72b8f1f1b5ba0b15aa26db902090000000326697be300 | ||
1 output(s) for total of 35.050343054870 HMNY
| stealth address | amount | amount idx | tag |
| 00: 1eaaf14dd7dd783eb34adfbc4c83c4172db73537dd262ffdc3055bf52980ac3a | 35.050343054870 | 2284 of 0 | <68> |
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": 2062,
"vin": [ {
"gen": {
"height": 2002
}
}
],
"vout": [ {
"amount": 35050343054870,
"target": {
"tagged_key": {
"key": "1eaaf14dd7dd783eb34adfbc4c83c4172db73537dd262ffdc3055bf52980ac3a",
"view_tag": "68"
}
}
}
],
"extra": [ 1, 232, 190, 236, 184, 64, 34, 134, 32, 236, 20, 181, 183, 120, 32, 169, 17, 246, 230, 202, 89, 199, 43, 143, 31, 27, 91, 160, 177, 90, 162, 109, 185, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}