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.
19ce872453921b2b7e600037224dae75a6943dc6c15cc19574ad135ced29524e
Both payments are on their chains and locked to the same secret hash 96bada88cd313cb76ec5bc7b7429a47919038bec, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 19ce872453921b2b7e600037224dae75a6943dc6c15cc19574ad135ced29524e
- MakerPaymentSpent: 11e5f54295c40cf1e6f0967f0a8c861fd232bee43824d53b7178800335bc91e5
59c9ff0c802185e6d8047a52b90a4f6c6d11bc5af54077b174b88ed936cb56aa
Both payments are on their chains and locked to the same secret hash 96bada88cd313cb76ec5bc7b7429a47919038bec, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 1339d0f5c97fbda121dbfdb167456a58bd0bd9f7161e2d258f2f41672edca06c
- TakerPaymentSent · TakerPaymentReceived: 59c9ff0c802185e6d8047a52b90a4f6c6d11bc5af54077b174b88ed936cb56aa
- TakerPaymentSpent: ff66a3e8db08eddfbc344726a32753d0a4bdda069990363a88c55149c991b49a
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.