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.
bac200860122c9fbd683867c3933b2c521d5698aa3c1f5b98e1b9db58f2e8027
Both payments are on their chains and locked to the same secret hash 3c95708ad7972fb9e9a3c9fca7fb6eb3bf1b8864, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: bac200860122c9fbd683867c3933b2c521d5698aa3c1f5b98e1b9db58f2e8027
- MakerPaymentSpent: 2c75463e520aec7e1418b3d518f0ce2facb3fb84c9664763c0ce1c78684c703a
a99b01719cd33b7dfc8f1c85d89105a6ecc3a2774943664c42434b5de57e25c4
Both payments are on their chains and locked to the same secret hash 3c95708ad7972fb9e9a3c9fca7fb6eb3bf1b8864, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: a5009d6c10d6cec0730a6aaadd2515df21a0fbe92a886d15f209d7d93528e231
- TakerPaymentSent · TakerPaymentReceived: a99b01719cd33b7dfc8f1c85d89105a6ecc3a2774943664c42434b5de57e25c4
- TakerPaymentSpent: 851aeb99830301f33d47d2b067c86767e3e8c60164eda8352e9131c9a686a482
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.