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.
615b1a9bd8ea0c71f88c19187f24c0969b0369663c1fdcae2d6ade5c12f03746
Both payments are on their chains and locked to the same secret hash 40df42d9bb52556425a8e7f0a7ecbc813c6f6382, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 615b1a9bd8ea0c71f88c19187f24c0969b0369663c1fdcae2d6ade5c12f03746
- MakerPaymentSpent: 2b80689f60b900b003ead4f374e030f99bd8492a11cb1bf1667e4617ec9ebbd6
ad94e1020f3e11cb8adf373096bca0dabc20c190e3122d5c67c4ef95f3f80fbc
Both payments are on their chains and locked to the same secret hash 40df42d9bb52556425a8e7f0a7ecbc813c6f6382, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 40829409712fea6ed14e78d3ea026c2cccded704a87149459e2de1e01c8d2a64
- TakerPaymentSent · TakerPaymentReceived: ad94e1020f3e11cb8adf373096bca0dabc20c190e3122d5c67c4ef95f3f80fbc
- TakerPaymentSpent: a904270dec2d8c8777ddf8eaa32e08570af7320e749454450532c6acb88311c5
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.