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.
0f9603a6095785483821a65a5eae5fadc1152b1dd10ba867d37fb5d6b612b20f
Both payments are on their chains and locked to the same secret hash 7cb1b5a10fd88ab422e499ea8f1b368e629b29fd, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 0f9603a6095785483821a65a5eae5fadc1152b1dd10ba867d37fb5d6b612b20f
- MakerPaymentSpent: 6fbeb44dc7f0935b42359645e18dbd4c3a458d539c9d79d7c0f27eb76cb37e40
a02042f86c09617b89ff953a44e0861ea989a2f754cab1656dad3316ed252a80
Both payments are on their chains and locked to the same secret hash 7cb1b5a10fd88ab422e499ea8f1b368e629b29fd, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: a9d173bcf46a83de72a657211e3f41e8aea948194dccfec883589308a4d4a854
- TakerPaymentSent · TakerPaymentReceived: a02042f86c09617b89ff953a44e0861ea989a2f754cab1656dad3316ed252a80
- TakerPaymentSpent: 36a427043e74406d17344d369ca0c5eb34662f9c6ac380aa45e72cb4bed0e816
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.