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.
dfd6e7472bf5374fc753fa4bf1ca08bd9aaab1d584a223ba73638a35e66fe7ad
Both payments are on their chains and locked to the same secret hash a00b23c0a156955391fae431815012e2ef6e82be, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: dfd6e7472bf5374fc753fa4bf1ca08bd9aaab1d584a223ba73638a35e66fe7ad
- MakerPaymentSpent: 13e99b59ce3d163ba9677e6d5c1b0533f5631d5d6b65dfb51fea7b3a322eba5f
5b5223a7b789b21ffe22f1ac5e0276e3acd1e895e60ea0e104bbc83b5a2d352a
Both payments are on their chains and locked to the same secret hash a00b23c0a156955391fae431815012e2ef6e82be, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: b12ea10c9c62355c17edc89e5efb9cc758a2d3ed12e4032a698e34bcee383d07
- TakerPaymentSent · TakerPaymentReceived: 5b5223a7b789b21ffe22f1ac5e0276e3acd1e895e60ea0e104bbc83b5a2d352a
- TakerPaymentSpent: 6466f88131ca0d5d6b70799c603e14c3d77f074b1bfe194007da01b70cb293c6
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.