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.
a1163dc98456dd02bef3c458d550c121bdd1282f3899943149d06278059ec616
Both payments are on their chains and locked to the same secret hash f8f7d1d3ce70bc3142ae62bddb4522dfd2f3fa83, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: a1163dc98456dd02bef3c458d550c121bdd1282f3899943149d06278059ec616
- MakerPaymentSpent: c5eadfca01e52ae80d75b3bca3770212ee51ef52f1be5bb63b11fccee8dc52e4
34447136a383239f7308758593b5ac2084dc9e3ad988ba72cfa32e500619efc4
Both payments are on their chains and locked to the same secret hash f8f7d1d3ce70bc3142ae62bddb4522dfd2f3fa83, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: c60167c810f29285010c84b02223f0daa3d7e9e3ddfb79f1ff413b9217ca56f3
- TakerPaymentSent · TakerPaymentReceived: 34447136a383239f7308758593b5ac2084dc9e3ad988ba72cfa32e500619efc4
- TakerPaymentSpent: 620442738285148917fe1895bc4314becc793acb2d86f931797fca0a5371112d
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.