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.
67b748d61d677ce3f4afa8ed908074bd011f9acd4fdb47bfbe64a1d286939186
Both payments are on their chains and locked to the same secret hash f666e328c45707d89238b276c36c7346b3260fbb, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 67b748d61d677ce3f4afa8ed908074bd011f9acd4fdb47bfbe64a1d286939186
- MakerPaymentSpent: 07ea1503bef41a6a6f814b48af517e07faf509110c48886c7d163d89c6b60d00
b692cebe482481f1eb9b59c161fa805786e99d91ba5938650b7b195983a383fe
Both payments are on their chains and locked to the same secret hash f666e328c45707d89238b276c36c7346b3260fbb, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 184c3b7727bd7a52664f0f10ca5decd49bf25d899502b42a165b8ae9a3223311
- TakerPaymentSent · TakerPaymentReceived: b692cebe482481f1eb9b59c161fa805786e99d91ba5938650b7b195983a383fe
- TakerPaymentSpent: cb5ed9099a7b41ce1e807609b42f7b238de27a5985e6086ee1d7833069bbede2
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.