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.
d73d638bb20161c8a526437c5bb6c2bb2940065bfb5a37a10a05d659951c35ec
Both payments are on their chains and locked to the same secret hash f1c5ed884c15a1bd153aa70310338fe55516baa8, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: d73d638bb20161c8a526437c5bb6c2bb2940065bfb5a37a10a05d659951c35ec
- MakerPaymentSpent: 8b638384c583a4dd27184744029147b926b7771b1917c0f87427d2bac7f7514a
aa1e5741e6e6abf5d235360dd64084fb97da011c9f0778d8c60d6a928d34356b
Both payments are on their chains and locked to the same secret hash f1c5ed884c15a1bd153aa70310338fe55516baa8, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: b344d542e99273b5606ea398248ea07202f9a52bf8493608ddee31f7f3f91ba9
- TakerPaymentSent · TakerPaymentReceived: aa1e5741e6e6abf5d235360dd64084fb97da011c9f0778d8c60d6a928d34356b
- TakerPaymentSpent: bad5a8c7b3916a78fab747056661923f444dda00aebc651fa87a39312479b453
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.