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.
26c9cb8d81ffb266efa7eccbcf3e3f7cf0d109a4efc4374603a36952471b50f8
Both payments are on their chains and locked to the same secret hash 171ac2ad7da9ab4b81d8842bfbb4a2375fea6a8f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 26c9cb8d81ffb266efa7eccbcf3e3f7cf0d109a4efc4374603a36952471b50f8
- MakerPaymentSpent: b86564339eeba98977448655778d7b4c8a3eea8d4d892462c9209c0c7c235de8
8e7d60d0dd44c8547dfd4eab95d49e8cb4d1666b6221eb5737ac344b5a63dcb4
Both payments are on their chains and locked to the same secret hash 171ac2ad7da9ab4b81d8842bfbb4a2375fea6a8f, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: eb8ed45e87a553c1a703bed38a1daed45405cd4a68d145c14b296cf033afc6c5
- TakerPaymentSent · TakerPaymentReceived: 8e7d60d0dd44c8547dfd4eab95d49e8cb4d1666b6221eb5737ac344b5a63dcb4
- TakerPaymentSpent: 8f29aa764077497af3e7b185017f863efc942b4654bd568824c198264099bd0c
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.