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.
621f85512849f5787843bf291d5ebcc4bd3d889977f5d110e5edd005679f53cf
Both payments are on their chains and locked to the same secret hash d6232354ee03eeef527c0e8abba4910001712c32, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 621f85512849f5787843bf291d5ebcc4bd3d889977f5d110e5edd005679f53cf
- MakerPaymentSpent: 72e1f1f36cfa2e26347c995af160504e0c3b2ff2af9f1fe97d6c62e57728ff06
611eb16789da7fa34fb7c2dbe6c5cccc36fde8abe190ab98976277b6c33a4451
Both payments are on their chains and locked to the same secret hash d6232354ee03eeef527c0e8abba4910001712c32, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 79ef86590e4b6a89f480fdc77727dbeab7c4879f9adc779266f704034a5d11fb
- TakerPaymentSent · TakerPaymentReceived: 611eb16789da7fa34fb7c2dbe6c5cccc36fde8abe190ab98976277b6c33a4451
- TakerPaymentSpent: 9b3017c079305225bd846616bec6b51b69072ccc8b8efeb35d10429aae881686
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.