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.
6b1191afb22bca2a730e887d2ebdec04c7e468fba8e5a4d2cecb7071a79c4af1
Both payments are on their chains and locked to the same secret hash fcaceb4564a52efbc54791b9f0f7a39a159076d6, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 6b1191afb22bca2a730e887d2ebdec04c7e468fba8e5a4d2cecb7071a79c4af1
- MakerPaymentSpent: b5b7b680b03ddf581cfa2f574bd5a72d32e4a9e8474b1bcb58145824b49e0747
3b7402588705807f8d52adc63069041c6320603bfeec4ff55a9b524a1c9ea1b4
Both payments are on their chains and locked to the same secret hash fcaceb4564a52efbc54791b9f0f7a39a159076d6, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: b6ff2446a6251c646a37037b2b19b8d89a48aba5ffea94df271e2454613d16d6
- TakerPaymentSent · TakerPaymentReceived: 3b7402588705807f8d52adc63069041c6320603bfeec4ff55a9b524a1c9ea1b4
- TakerPaymentSpent: 9972877b91bec3a3f39f1466f5943f79b99957c8566363afe86961947c0a64f1
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.