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.
cad0053c343b77cb70bac4de558785ca942cb0ab1111448f191bd7ee583cc8c0
Both payments are on their chains and locked to the same secret hash 8e9637ec5ba2dbc27b25a822ff67a1a3d28bdaa1, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: cad0053c343b77cb70bac4de558785ca942cb0ab1111448f191bd7ee583cc8c0
- MakerPaymentSpent: 2278f8a0e32640efa0a8251fca9742877b47e4e5e7196035598b7200eb69ba2d
2e0e89fc2cd71eeefd5709c7e0ed5886037bafafa0a4e855baee25c19c9e2c22
Both payments are on their chains and locked to the same secret hash 8e9637ec5ba2dbc27b25a822ff67a1a3d28bdaa1, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: 50dca53139cfe115364dbaef8439bffc84e40fdeced1efbe5375387ed7114deb
- TakerPaymentSent · TakerPaymentReceived: 2e0e89fc2cd71eeefd5709c7e0ed5886037bafafa0a4e855baee25c19c9e2c22
- TakerPaymentSpent: 19e71b0ccd528a29c474d0863334e4277f611cabb57efc1cae1024a40e71e003
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.