16jX5RbF2pEcLYHPukazWhDCkxXTs7ZCxB
Sign in to watch
Alert when money comes in or goes out, as soon as the transaction shows up.
Observable history
- Received
- 7 BTC
- Sent
- 7 BTC
- Balance
- 0 BTC
- Transactions
- 6
- First activity
- 12 Oct 2016
- Last activity
- 24 Nov 2016
Checked on 19 Nov 2026 · Source: chain
Transactions
The effect is the net change for the address: positive came in, negative went out.
| Date | txid | Effect on the address | Source |
|---|---|---|---|
| 24 Nov 2016 | f41e402dfa…d445e6d8 | -5 BTC | chain |
| 14 Nov 2016 | 1452ffe76c…633bbe4f | -2 BTC | chain |
| 20 Oct 2016 | 0a4a07db1a…8421a6eb | +2 BTC | chain |
| 12 Oct 2016 | 9b379d19ab…d4bb7829 | +1 BTC | chain |
| 12 Oct 2016 | 6d53d25b83…eafb8aad | +2 BTC | chain |
| 12 Oct 2016 | f21475d1b2…539995e5 | +2 BTC | chain |
Attributions
- reported as a ransom address of XTPLocker 5.0 Ransomware · corroborated, medium · source statement · recorded by automated process · reviewed
Ransomware families
How to read this
- An incoming transaction to an address reported as a ransom address is not a proven payment: only a payment report with evidence allows saying so.
- Whoever sent the money is not labelled: it may be the victim.
- Association is not control: the source links the address to a family or entity, it does not say who controls the wallet.
- Amounts in BTC, as recorded on chain; the price in local currency or dollars varies and is not included.