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.
af288844aaed91dad96641fc2bc6128278a198ad85346cc1b49d19c9a28384d6
Both payments are on their chains and locked to the same secret hash 48ba871e7830c2ae927bf685d94f91f4a0993161, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: af288844aaed91dad96641fc2bc6128278a198ad85346cc1b49d19c9a28384d6
- MakerPaymentSpent: e874f27725cdc355531440bae0d9deee3d4a1ff6a3df345936ce66eb1b0b174c
46bfbf7b48557382f2f60a8a95bf64f8489fa0db2e8acb24589d242f5415bc10
Both payments are on their chains and locked to the same secret hash 48ba871e7830c2ae927bf685d94f91f4a0993161, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 48f7b41a7bc78282388890062a4d7ed23418cc7ba220200d94b40daeb3b3b897
- TakerPaymentSent · TakerPaymentReceived: 46bfbf7b48557382f2f60a8a95bf64f8489fa0db2e8acb24589d242f5415bc10
- TakerPaymentSpent: edadb40186034ad2bad256fae528b6e9a063bbed01296018a006f11b87ba2476
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.