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.
cb4ad0b0a105eeffa6850bfe36f038b231eb2f3b5f766127894e0dcd593abed8
Both payments are on their chains and locked to the same secret hash 801b118494bdab51bd18fe3558126eb960470735, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived: cb4ad0b0a105eeffa6850bfe36f038b231eb2f3b5f766127894e0dcd593abed8
- MakerPaymentSpent: d79cda9b4dd6b7da68afb9b9fd90fba02234267ac7a0f8cdc4da92c663d87f1c
e812a8b768c79f615089831410b252942e4a2397cc66494f528b1b4a37eef602
Both payments are on their chains and locked to the same secret hash 801b118494bdab51bd18fe3558126eb960470735, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent: 56f8f2f965214902e40b99f0ff098dec7b71a70b0a1e199bbe46284ae06d1f40
- TakerPaymentSent: e812a8b768c79f615089831410b252942e4a2397cc66494f528b1b4a37eef602
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.