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.
3872dcd53fda75e1e55f48eef69abeb3ee8d3b6e27f42ad9afe37c361c7bfcb3
Both payments are on their chains and locked to the same secret hash f71ab845d1d72809df792ff4a4d858210a1aaeb1, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 3872dcd53fda75e1e55f48eef69abeb3ee8d3b6e27f42ad9afe37c361c7bfcb3
- MakerPaymentSpent: 449e098a9a121a59dc06e60a7a02c6c42419c83e445d2feb6852cbb823f978f6
136a7d38e0da950624da9373c8dfa9cbecdbad799220aca746e3ce9b21c57f1b
Both payments are on their chains and locked to the same secret hash f71ab845d1d72809df792ff4a4d858210a1aaeb1, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 0271d788ac1e86a49bb34af2efbeb71531ea93e930ab557f3ed43e5773f48e4b
- TakerPaymentSent · TakerPaymentReceived: 136a7d38e0da950624da9373c8dfa9cbecdbad799220aca746e3ce9b21c57f1b
- TakerPaymentSpent: 3b4f60cdf510bf3a8b8b91fc3dd3eec713dcde5fdeec04312cfb7669706f598d
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.