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.
8b48b0c7d85493f6d6958d1a9d6cb53f6d5654c2076d4ed780ca44b9864e4362
Both payments are on their chains and locked to the same secret hash 208968dccb866c85dcd8b3b754308a447a1edf58, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 8b48b0c7d85493f6d6958d1a9d6cb53f6d5654c2076d4ed780ca44b9864e4362
- MakerPaymentSpent: 332b25b5d1437c2ca179d26af031dc0efa3d858b7bfd1ba15cb0bf40f0ac9fcc
339617515dde9dbe543fdc9d2113e868652eef58829f851c4f7fd7fb7cd0bad7
Both payments are on their chains and locked to the same secret hash 208968dccb866c85dcd8b3b754308a447a1edf58, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 7300bab77b894b94855e2885dbe7a19d622d6bc3899838dc9efcba02ed59c5d0
- TakerPaymentSent · TakerPaymentReceived: 339617515dde9dbe543fdc9d2113e868652eef58829f851c4f7fd7fb7cd0bad7
- TakerPaymentSpent: dfec8f177044fd4eee39a314e19fbda734936bddfdec07a4697056b017402956
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.