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.
8fdd5ab3786c63ea99fe87b35c9ca651139ee15b959193ef173b8e1b15852203
Both payments are on their chains and locked to the same secret hash 8c30b31367067437207ca359c73ffd8fa2bea848, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 8fdd5ab3786c63ea99fe87b35c9ca651139ee15b959193ef173b8e1b15852203
- MakerPaymentSpent: 06efa6b981a6ca31dbb8143e3fefcdf58e91a19f145f4cc49ec72e6595ea7ad6
ef6e191df419c81c032fd77427bcba288c794a07514cac3f21cd4431f87c5720
Both payments are on their chains and locked to the same secret hash 8c30b31367067437207ca359c73ffd8fa2bea848, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: dcbfc380d5a27d88962371ff62cacc23e96fed3ee6669248ed14d0f761662bd4
- TakerPaymentSent · TakerPaymentReceived: ef6e191df419c81c032fd77427bcba288c794a07514cac3f21cd4431f87c5720
- TakerPaymentSpent: bdc29a802b11575da10e13cfbfc8019ab8f5d083f703bb05c18e50216c0bb329
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.