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: b975f291ed63f75871eb7da33657938e4f774ed6ba97873b0c58ea5ac62d2268
Tx prefix hash: afd2acadf4d26e005d8407e77c2cdbe93c796b914e5604ca31d56ca9bd759725
Tx public key: cb18de8635d94ada4f49801cdf84382edd8e16e66abfd823fead3c69387fe3f8
| Timestamp: 1779854195 | Timestamp [UTC]: 2026-05-27 03:56:35 | Age [y:d:h:m:s]: 00:012:20:50:12 |
| Block: 2591 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5295 | RingCT/type: yes/0 |
| Extra: 01cb18de8635d94ada4f49801cdf84382edd8e16e66abfd823fead3c69387fe3f802090000000126697be300 | ||
1 output(s) for total of 35.010988578565 HMNY
| stealth address | amount | amount idx | tag |
| 00: da534cef4d03c8807816c379b769e6b30f188934a087b435726f1417d7ff626d | 35.010988578565 | 3049 of 0 | <d8> |
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": 2651,
"vin": [ {
"gen": {
"height": 2591
}
}
],
"vout": [ {
"amount": 35010988578565,
"target": {
"tagged_key": {
"key": "da534cef4d03c8807816c379b769e6b30f188934a087b435726f1417d7ff626d",
"view_tag": "d8"
}
}
}
],
"extra": [ 1, 203, 24, 222, 134, 53, 217, 74, 218, 79, 73, 128, 28, 223, 132, 56, 46, 221, 142, 22, 230, 106, 191, 216, 35, 254, 173, 60, 105, 56, 127, 227, 248, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}