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: 0884880694f8eb9174ef8af9651cf9e8110ef9473fb74299d53fb54158828232
Tx prefix hash: cb88f9a669dac39128d4ee9ff771c09e15ccb0f38aeddae249324f879bee22f2
Tx public key: 02c636bd764c2e5861735c88b4858f26def22b0c619892dd1e3fae915a9139b9
| Timestamp: 1780114279 | Timestamp [UTC]: 2026-05-30 04:11:19 | Age [y:d:h:m:s]: 00:009:19:07:34 |
| Block: 4870 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3016 | RingCT/type: yes/0 |
| Extra: 0102c636bd764c2e5861735c88b4858f26def22b0c619892dd1e3fae915a9139b902090000000426697be300 | ||
1 output(s) for total of 34.862551293715 HMNY
| stealth address | amount | amount idx | tag |
| 00: df8d3d5a6d1a794f7860c5e935d401cf34a63e613b50ac5bca2819ea5b7bd67f | 34.862551293715 | 6152 of 0 | <ee> |
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": 4930,
"vin": [ {
"gen": {
"height": 4870
}
}
],
"vout": [ {
"amount": 34862551293715,
"target": {
"tagged_key": {
"key": "df8d3d5a6d1a794f7860c5e935d401cf34a63e613b50ac5bca2819ea5b7bd67f",
"view_tag": "ee"
}
}
}
],
"extra": [ 1, 2, 198, 54, 189, 118, 76, 46, 88, 97, 115, 92, 136, 180, 133, 143, 38, 222, 242, 43, 12, 97, 152, 146, 221, 30, 63, 174, 145, 90, 145, 57, 185, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}