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.
5185553ddfc28befc967ee237f596baa9e3cd73668d245a56081d8d53cd49b3a
Both payments are on their chains and locked to the same secret hash c407c09507fa100fffe0aff40371f1e23852bf9d, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 5185553ddfc28befc967ee237f596baa9e3cd73668d245a56081d8d53cd49b3a
cf4529dec5892ca4b414f50446080d5d92045c280011a3afcfc127df8fc93562
Both payments are on their chains and locked to the same secret hash c407c09507fa100fffe0aff40371f1e23852bf9d, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 66c9776cb2d4af99ac15da2aa56cf6d0b615ad47c5925ca03ac2fc7769bbdd0f
- TakerPaymentReceived: cf4529dec5892ca4b414f50446080d5d92045c280011a3afcfc127df8fc93562
- TakerPaymentSpent: f8d369b72deb59489f42fe549afb9931324ac743f1698c79b1aaacb5530db7b4
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.