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.
908e6d7ecf8e9e7b3bc4ae22f98f3788bc24e44a48be0677bedee9cb13a9b59f
Both payments are on their chains and locked to the same secret hash 3e0cb89a6c4412372693aafbf612bdbe8b4b3ec9, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 908e6d7ecf8e9e7b3bc4ae22f98f3788bc24e44a48be0677bedee9cb13a9b59f
- MakerPaymentSpent: 6746a05a760666aa00061ca08fc8d1632f2e945a31815c0913e17b3230398dd9
4449bc86d9e4819facfcdbb3927641e8b1f46b06e7b8b14114358d891103976c
Both payments are on their chains and locked to the same secret hash 3e0cb89a6c4412372693aafbf612bdbe8b4b3ec9, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 6ec7df5f9b52b6a43e36231279b838a6a4651f045650ac8d287bbbf49f47b820
- TakerPaymentSent · TakerPaymentReceived: 4449bc86d9e4819facfcdbb3927641e8b1f46b06e7b8b14114358d891103976c
- TakerPaymentSpent: a61961341b376b46ad305fdc35d1535778e9ad88376ad5e019b525de37868888
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.