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.
a573df06d5407cf2b3a7b5357f8338ac1afd6a45d1e2f22162ebb4ffbe9794ae
Both payments are on their chains and locked to the same secret hash 5c8d7a6157a5a3709e894830a65d665fc5cffacc, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: a573df06d5407cf2b3a7b5357f8338ac1afd6a45d1e2f22162ebb4ffbe9794ae
- MakerPaymentSpent: e932291c81a49dfd31b7e8583c7b1c8ebf1370ab0086b08d775e4e184dfe6f47
4e4d26095d01838412f994d31a883d76b0a2b0970f9d4e58989c572cee45205c
Both payments are on their chains and locked to the same secret hash 5c8d7a6157a5a3709e894830a65d665fc5cffacc, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 505dfa20fc2e1bafc778f0ffd49c06865ec9862f520806f62d5c2e6080c99198
- TakerPaymentSent · TakerPaymentReceived: 4e4d26095d01838412f994d31a883d76b0a2b0970f9d4e58989c572cee45205c
- TakerPaymentSpent: a513a984ac4fe07455cbb57f37eb52f801c3239be8786d3c2e896da2ea9b4bfa
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.