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.
43e30eda45d41a3053fe8b8b1f5052aff1e4ef2a6118cde7127fbb38c8d87564
Both payments are on their chains and locked to the same secret hash b9f598bd86639784806716b71ec8817ee59c653d, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 43e30eda45d41a3053fe8b8b1f5052aff1e4ef2a6118cde7127fbb38c8d87564
- MakerPaymentSpent: 275c4210979b907fb6e3247e2082c7fe3cef4640e9b1e0d329afd54a80ee12f5
bcc2432189b8e653eb74fe7731c342fcdacf729722d7b40619ab14119b0a1b85
Both payments are on their chains and locked to the same secret hash b9f598bd86639784806716b71ec8817ee59c653d, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 7ccebd59b1e9893ec0d3b494c691d6e2344250f0971a367aecbd17b002fa9230
- TakerPaymentSent · TakerPaymentReceived: bcc2432189b8e653eb74fe7731c342fcdacf729722d7b40619ab14119b0a1b85
- TakerPaymentSpent: 6b9386c3fa142b916941328292bca4a5ed53e16af261d74d25214c85fccb5711
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.