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.
2b91f68d900309f0b9300d9ed2324396a047fffc2710a8c34e05bb6d4fc49bad
Both payments are on their chains and locked to the same secret hash 510e97020327290d7e89e5746e92faa1e89ee663, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 2b91f68d900309f0b9300d9ed2324396a047fffc2710a8c34e05bb6d4fc49bad
- MakerPaymentSpent: d277a88b401a9ef1c5c781635f7d0fefb54badbe6d94593d11084708345b47e2
cea7639c81a915b91952b4148a0d4dc09892c1856e5e49ad7364eb46e6b07b80
Both payments are on their chains and locked to the same secret hash 510e97020327290d7e89e5746e92faa1e89ee663, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: c162d6fa1eed61086960c1a3ca93170240a1c1dcc276b0ce171738c5debd325e
- TakerPaymentSent · TakerPaymentReceived: cea7639c81a915b91952b4148a0d4dc09892c1856e5e49ad7364eb46e6b07b80
- TakerPaymentSpent: 5d694e767442eea47d87fde62d0b95814b118761e6a7d19b232720f579921fa6
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.