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.
5cca5e45e07df0731b3a494db7cb2480eb2e3c8f6ea003d7c5fa13d4b3e180a0
Both payments are on their chains and locked to the same secret hash 3876be22d4ee1d307d400e387a591517d67c305f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 5cca5e45e07df0731b3a494db7cb2480eb2e3c8f6ea003d7c5fa13d4b3e180a0
- MakerPaymentSpent: b64ceb8e7235d67cd00d444ab917954bd5920bed4d916dde36dbe8636e020012
6dc0e6080bc3715bb002c9b4335541c4e63ccf6133d0afe5b3b8bd9ddb6ff102
Both payments are on their chains and locked to the same secret hash 3876be22d4ee1d307d400e387a591517d67c305f, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: f9c296dadf7322d73d0f8b9fee4aa74530822b01f21dd0bcaf96022a3ea9d2fa
- TakerPaymentSent · TakerPaymentReceived: 6dc0e6080bc3715bb002c9b4335541c4e63ccf6133d0afe5b3b8bd9ddb6ff102
- TakerPaymentSpent: 0a4e66c34694091ecb65371a9e94a90374eb9f8bcac56db1343c429f72415be8
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.