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.
ca1ad48f518f210523195589097cf2299120d685497befcde699d013e9021012
Both payments are on their chains and locked to the same secret hash 3c0f0d5a093748823593900c7ba20ad9c1decde8, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: ca1ad48f518f210523195589097cf2299120d685497befcde699d013e9021012
- MakerPaymentSpent: 2ba8ca5c9bc6bc020a2e0d1faead83c608a29c30525bb79228596d7e8263976e
bf042e817d46ceee7008b9b7c656656bb6682f2208607a8a074775c562e5d7dd
Both payments are on their chains and locked to the same secret hash 3c0f0d5a093748823593900c7ba20ad9c1decde8, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: de15f400ec896f48dc629559c16288bbdf127dfd2ed25d14837c4cec86a8a03c
- TakerPaymentSent · TakerPaymentReceived: bf042e817d46ceee7008b9b7c656656bb6682f2208607a8a074775c562e5d7dd
- TakerPaymentSpent: abcd460731cd58db44ff4c65f50b91f8cd1cbb0b291bb13954d162f17a8b7d69
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.