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.
e8592675ec6b5ec5cea5caebc8323b6f78555f897874f4d59e8f334d2af634ed
Both payments are on their chains and locked to the same secret hash 5d43c26e3c9b67d49a2a199aba0419f0e41feeb6, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: e8592675ec6b5ec5cea5caebc8323b6f78555f897874f4d59e8f334d2af634ed
- MakerPaymentSpent: b824992d4c1c2742f9431ca7345bcda682ffdfb78059b2349328cfb4be8ec1b2
a447cc11698c4cdaa45114dbef292112eff6c07752093aebe13598a1337dafb8
Both payments are on their chains and locked to the same secret hash 5d43c26e3c9b67d49a2a199aba0419f0e41feeb6, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 870e9d646dc113432404151407bc04fb1b7726343c81977ea9e84e36d902267b
- TakerPaymentSent · TakerPaymentReceived: a447cc11698c4cdaa45114dbef292112eff6c07752093aebe13598a1337dafb8
- TakerPaymentSpent: 42767868c5a4b537b55c86a18a24914c8a33cc6b4e8d6005bda47e73f12ca633
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.