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.
f3308a476bffc261d3ef78cd873feb1da4bedad3fc12f1fa15e999b17885d9c3
Both payments are on their chains and locked to the same secret hash 527b48766de2d357e4a87e391f2ffdd94497152d, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: f3308a476bffc261d3ef78cd873feb1da4bedad3fc12f1fa15e999b17885d9c3
- MakerPaymentSpent: af2fcb0cf122c3a5d48765b2ec1d91bbaef58eaac357bc1b03424ba9de310563
bf0961c5759dc3739f1a56b17e4650525d987c3573f8798ba085fcb71bff7fe6
Both payments are on their chains and locked to the same secret hash 527b48766de2d357e4a87e391f2ffdd94497152d, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 7a65ce89eb0745d426af1efafb49c51cb37e430744d9206e2fb3d1a5272f953f
- TakerPaymentSent · TakerPaymentReceived: bf0961c5759dc3739f1a56b17e4650525d987c3573f8798ba085fcb71bff7fe6
- TakerPaymentSpent: 3a893ac56658c289dbc611c3bd80bcb1c00524242c1b71b738fb9e672e1232f6
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.