An atomic swap is not instant by design. Each side has to publish a transaction and wait for the other chain to confirm it, so the time it takes is set mostly by the block spacing of the two chains involved rather than by anything either party does.
1c1eeb453def57992859352feeb234c8d3b196b19622b8e4696eaf5f939d93c0
Both payments are on their chains and locked to the same secret hash cf8392b7881342d0761829ea575f94a901cb8643, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 1c1eeb453def57992859352feeb234c8d3b196b19622b8e4696eaf5f939d93c0
- MakerPaymentSpent: 243ffc1911ac12b7e619f8e7d9165d0aa9bfa8054a38ee24671cd72395e50e21
a0c9b2949f8af36dc5a87e06953f295ea2332ece103122e49ddfe9ce5f0f29df
Both payments are on their chains and locked to the same secret hash cf8392b7881342d0761829ea575f94a901cb8643, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 59b93beb535323ed820ad4d88f16ea6a5f7d44b8712b59c9e3c5c43c5e122b47
- TakerPaymentSent · TakerPaymentReceived: a0c9b2949f8af36dc5a87e06953f295ea2332ece103122e49ddfe9ce5f0f29df
- TakerPaymentSpent: 675c74d5cb83d59d39ffcffa6d138ed1909b2e052bb9b082ce2bcf90bbcfb0a9
No flags are stored against this swap. Flags are written while a swap sits inside a live pricing window, so on an older swap their absence means it was never assessed rather than that it was assessed and found clean.
Reported by kdf-statsdb-8762.