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: ed2cfb36bc9022ef661e4caf9fce8038336a5e9ddf6510a599fcb4aa2bbf26cb
Tx prefix hash: f3dad7d390c9add55fa3158336e7e9b25db9449d6e71d90b73b9d9a0cffe1802
Tx public key: 4ed576ee0901a3fc094538c17f7b1cace28b77f43750ca576dd4a92470074677
| Timestamp: 1780693203 | Timestamp [UTC]: 2026-06-05 21:00:03 | Age [y:d:h:m:s]: 00:003:20:09:00 |
| Block: 5854 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2880 | RingCT/type: yes/0 |
| Extra: 014ed576ee0901a3fc094538c17f7b1cace28b77f43750ca576dd4a92470074677020900000001e49593ff00 | ||
1 output(s) for total of 34.793767888450 HMNY
| stealth address | amount | amount idx | tag |
| 00: 34040500cf88b42e533a4d18480fec5f7a7fb183af297241709253d77e409c12 | 34.793767888450 | 7313 of 0 | <e0> |
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": 5914,
"vin": [ {
"gen": {
"height": 5854
}
}
],
"vout": [ {
"amount": 34793767888450,
"target": {
"tagged_key": {
"key": "34040500cf88b42e533a4d18480fec5f7a7fb183af297241709253d77e409c12",
"view_tag": "e0"
}
}
}
],
"extra": [ 1, 78, 213, 118, 238, 9, 1, 163, 252, 9, 69, 56, 193, 127, 123, 28, 172, 226, 139, 119, 244, 55, 80, 202, 87, 109, 212, 169, 36, 112, 7, 70, 119, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}