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.
3de5655b5d72ab5434eda14df607dbc78cae488e167a71d4e2c3532a6f93637c
Both payments are on their chains and locked to the same secret hash fc0843c28defe698124f2683e9d6664230cfe0a1, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 3de5655b5d72ab5434eda14df607dbc78cae488e167a71d4e2c3532a6f93637c
- MakerPaymentSpent: 626bfc2d2060f549033149aada2298af8f26988aeafbe77b5fbe9902e0be48fc
e65926e6abd1ece17b893b3c8eddb581a99c3deeda82db14fda41ecf3966a8d1
Both payments are on their chains and locked to the same secret hash fc0843c28defe698124f2683e9d6664230cfe0a1, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 8d746278503e29c93aedf589633c740a2ec886351eb5c944dd465a55f9cd0d85
- TakerPaymentSent · TakerPaymentReceived: e65926e6abd1ece17b893b3c8eddb581a99c3deeda82db14fda41ecf3966a8d1
- TakerPaymentSpent: 2c24a146785524b7ac1cc8c0b4ef822c9f408a9c349accfd771afa77751de168
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.