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.
21e3011946acd40b39e609b4e43f38aed5b59967ea46bfb541cc74db39961118
Both payments are on their chains and locked to the same secret hash f34178ee67fa918e33a926b3826981ea3e1f37c1, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 21e3011946acd40b39e609b4e43f38aed5b59967ea46bfb541cc74db39961118
- MakerPaymentSpent: bc07df001327db859c88e9484ff37f5288ae89d88616aa64df43765e8a6f062b
07d590985f70f66a6b94d771bb7354ed521f129083c7e0f6c3a5f40ab00ac927
Both payments are on their chains and locked to the same secret hash f34178ee67fa918e33a926b3826981ea3e1f37c1, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: 82fb73e8cc0c794b75459aad96904c1cb42eb3ca3c108f4f0e9e43607537eb9b
- TakerPaymentReceived · TakerPaymentSent: 07d590985f70f66a6b94d771bb7354ed521f129083c7e0f6c3a5f40ab00ac927
- TakerPaymentSpent: 77bd101e4eb571a2973ee886fc36842edb72ca74fd89823a5a387999468b0d95
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.