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.
0bb94baa60a438aac41a94b8b8dce4f3271adfc819fa0248c11640e3411c2ecc
Both payments are on their chains and locked to the same secret hash d4634b0eb9c1b49ed64f6ec7c36bc3e80436b66d, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 0bb94baa60a438aac41a94b8b8dce4f3271adfc819fa0248c11640e3411c2ecc
- MakerPaymentSpent: 5794eed9b540819929920c882a0f8e9627f6e94fdbabe583bee0d5f4e0db4e97
0784f2e97bb44ea1a40d4ab91dc025453d5055a9c3c6f97fe1606acd34259ee5
Both payments are on their chains and locked to the same secret hash d4634b0eb9c1b49ed64f6ec7c36bc3e80436b66d, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: e4a969fefce8159c5b6c4d58dcbdaefbda9317acbbf12f4d367e44ffdc021a25
- TakerPaymentSent · TakerPaymentReceived: 0784f2e97bb44ea1a40d4ab91dc025453d5055a9c3c6f97fe1606acd34259ee5
- TakerPaymentSpent: e0f5a657ae013e487d32ee2ce53f406a61612b646b99a48ddaf326a40777bd0c
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.