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.
dbb027a94990d7dcb812b752a37bce19eea7d494413c2ad2ae3a83dd512e1641
Both payments are on their chains and locked to the same secret hash 07ad72c9e4fa5f75e0aab9bab4bf2a33e5e162ed, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: dbb027a94990d7dcb812b752a37bce19eea7d494413c2ad2ae3a83dd512e1641
- MakerPaymentSpent: 8f1069eb0f581cf59277975fd1c2d6c8fc5bd35cdebbb34d4f491734a45e46a1
091451654419b96579aa334f819f9b3e3dc6086c39a0507b2ed218ac428bdfd9
Both payments are on their chains and locked to the same secret hash 07ad72c9e4fa5f75e0aab9bab4bf2a33e5e162ed, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 13e13765577814d744726c184a1ece3cba31887564d3f77d8cd58b4552ed562c
- TakerPaymentSent · TakerPaymentReceived: 091451654419b96579aa334f819f9b3e3dc6086c39a0507b2ed218ac428bdfd9
- TakerPaymentSpent: bc5719401782cfeb852f2bc6d9ecb2a2aed8828a47da36e1543ee1453e1b3eca
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.