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: 5d5a6c62f98fe6cce43982bdb396ca0392aa3f2b702028588d0228f6dc9d8217
Tx prefix hash: abe63909f28e832ecf11bb574bc7c205754cb1fdaf0d8b6e09fb102e6ab392bf
Tx public key: 5a70c6a4aabd48e5e87d2710aab2ec58f17d8557caaa3079dd464dbf24737d37
| Timestamp: 1779444904 | Timestamp [UTC]: 2026-05-22 10:15:04 | Age [y:d:h:m:s]: 00:017:16:25:32 |
| Block: 263 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7634 | RingCT/type: yes/0 |
| Extra: 015a70c6a4aabd48e5e87d2710aab2ec58f17d8557caaa3079dd464dbf24737d370209000000014438f87f00 | ||
1 output(s) for total of 35.166793942302 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8c4775ca149f891f4767c77fff893a12016b6f34c0620da9f542a4497ed31f88 | 35.166793942302 | 259 of 0 | <23> |
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": 323,
"vin": [ {
"gen": {
"height": 263
}
}
],
"vout": [ {
"amount": 35166793942302,
"target": {
"tagged_key": {
"key": "8c4775ca149f891f4767c77fff893a12016b6f34c0620da9f542a4497ed31f88",
"view_tag": "23"
}
}
}
],
"extra": [ 1, 90, 112, 198, 164, 170, 189, 72, 229, 232, 125, 39, 16, 170, 178, 236, 88, 241, 125, 133, 87, 202, 170, 48, 121, 221, 70, 77, 191, 36, 115, 125, 55, 2, 9, 0, 0, 0, 1, 68, 56, 248, 127, 0
],
"rct_signatures": {
"type": 0
}
}