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.
bea5ea8bf281833afd24e045dbdf8020ff9a1dd313184886e140afb5fa5e204c
Both payments are on their chains and locked to the same secret hash 1fc243c88201691722da8923e0508c6f7067f3ed, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: bea5ea8bf281833afd24e045dbdf8020ff9a1dd313184886e140afb5fa5e204c
- MakerPaymentSpent: 550e10bc0c7f71035c776ccb2fc749674d64a380bddffe014e31b1c102a45fa5
64b73bbc2904893be781f5a6e00ae0816601aa5fffa343b89a48021577a7318b
Both payments are on their chains and locked to the same secret hash 1fc243c88201691722da8923e0508c6f7067f3ed, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 3cbbcc08e3a9e7ef6f1845b65355cec821dddb3edc97fa8a17aeb960192e0e8d
- TakerPaymentSent · TakerPaymentReceived: 64b73bbc2904893be781f5a6e00ae0816601aa5fffa343b89a48021577a7318b
- TakerPaymentSpent: d3ba718c87923d0f406889270c495ffa4d81de371b8f9efd5c2e4ff475c1ab86
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.