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.
ab909054ad3d7a4484f536ba81006fe1e53bcf606e4168daff40a7472f55c853
Both payments are on their chains and locked to the same secret hash e74cb4bf0bf000d7b4e7a390682eebcec33a0acf, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: ab909054ad3d7a4484f536ba81006fe1e53bcf606e4168daff40a7472f55c853
- MakerPaymentSpent: 9cd91a003d516d6b2270696c645bb19d77d7ab4e51e27ba133dd7663462fdc2e
b2fac679e4827890c145e397904c0318c28e76f56061d1df317ed8fc12317c28
Both payments are on their chains and locked to the same secret hash e74cb4bf0bf000d7b4e7a390682eebcec33a0acf, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: f6c4f898075ba24d7145da2e95b56f769bed826c6d953e45489c9dbe4eff5435
- TakerPaymentSent · TakerPaymentReceived: b2fac679e4827890c145e397904c0318c28e76f56061d1df317ed8fc12317c28
- TakerPaymentSpent: 4a316603dd2165e17b9fbda26f3ba1f3657b57f8c976c4384aa6031bfb1350c0
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.