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.
0f6f26b8cd9f4c2700f805de5299285832760c5fe19525ca3669feedeab7a6e4
Both payments are on their chains and locked to the same secret hash 0ecfb693722c6d8b1b9a01ab61bc3caf37b5223d, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 0f6f26b8cd9f4c2700f805de5299285832760c5fe19525ca3669feedeab7a6e4
- MakerPaymentSpent: 713356f480ce5e444909e2e4b599a54b35cbb9bc680c80b7f757573dae843cbc
8621e1ca2142839ce0efd12f910fb34fc2eac7744ac697ef8186533c26557242
Both payments are on their chains and locked to the same secret hash 0ecfb693722c6d8b1b9a01ab61bc3caf37b5223d, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 690296b9ace062cfd7e44699be305d51813fc556b63e9d5fbab5ea98b32d5039
- TakerPaymentSent · TakerPaymentReceived: 8621e1ca2142839ce0efd12f910fb34fc2eac7744ac697ef8186533c26557242
- TakerPaymentSpent: d78ae846142f4a7b547c1e690f2dfdb9764fab37f7ef72927109ad895d3a9851
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.