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.
2ff67105ec7460cc9cf158ed5bdcc00beecc51254355e3db09aaf1b16a89f592
Both payments are on their chains and locked to the same secret hash 6024ef3cfc9e5b17c131df3a8f3ebb23137b0bc5, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 2ff67105ec7460cc9cf158ed5bdcc00beecc51254355e3db09aaf1b16a89f592
- MakerPaymentSpent: 5cfca4eb4562f7bbe60779da1c56cf8c0d1496e0beb40ad0fc199c17bad7b0f6
f5ecf839782065a7137da99f5231295377956557af233ffdd2cb0d3bffdfb5a8
Both payments are on their chains and locked to the same secret hash 6024ef3cfc9e5b17c131df3a8f3ebb23137b0bc5, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: e9932c03e244634d8ae7f07f48c5f7a1f3cc30a6bfde659fb9214b3300927fd7
- TakerPaymentReceived · TakerPaymentSent: f5ecf839782065a7137da99f5231295377956557af233ffdd2cb0d3bffdfb5a8
- TakerPaymentSpent: ee4215b781f64a19bf42648ec6adcd1c061338262713382f19aefaca9f21f428
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.