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.
682401f9b0def8b344c21484b75d22f0a153776e88f6013ae925074e69842323
Both payments are on their chains and locked to the same secret hash 60aeeac13fb87278f5ef79d28d8a3fb0fc1cf2d5, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 682401f9b0def8b344c21484b75d22f0a153776e88f6013ae925074e69842323
- MakerPaymentSpent: 89ed753c9c059068fd5f5bfa016b2d914578bd1d3fcc1bcf22bfb0963b41d172
8f41dd01f6cf9d7a62d4e2acf56f0005c21df1635b11ac14e4ca4857c409cf5c
Both payments are on their chains and locked to the same secret hash 60aeeac13fb87278f5ef79d28d8a3fb0fc1cf2d5, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 760720ee64e214349cedded6166e6be116b5c44ad174f567e7580b8893757b80
- TakerPaymentSent · TakerPaymentReceived: 8f41dd01f6cf9d7a62d4e2acf56f0005c21df1635b11ac14e4ca4857c409cf5c
- TakerPaymentSpent: d6dfc214231119654f94e4149cc482c6874d0b6dc21d0b652a9f0a6b63198e37
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.