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.
30e31d8fa8e5327d2db8fb5831301be56a43aef8df1e7f4a5ad5ad3ec5c6303a
Both payments are on their chains and locked to the same secret hash 2933bba04d4a5cd4643c2dac58a6ea526e054828, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 30e31d8fa8e5327d2db8fb5831301be56a43aef8df1e7f4a5ad5ad3ec5c6303a
- MakerPaymentSpent: c297d685aa5839da9a043e9512383e18e75d0bf6c90554fa1ece98b9e4b811e5
86a8bbf43b43a6ae0a7945779f757d8fe71c5d2992ed21322776564b5a2a1e79
Both payments are on their chains and locked to the same secret hash 2933bba04d4a5cd4643c2dac58a6ea526e054828, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 8c000c374207e359c07b5f1da3013af7a221a47e26d193945d09219dabecd094
- TakerPaymentSent · TakerPaymentReceived: 86a8bbf43b43a6ae0a7945779f757d8fe71c5d2992ed21322776564b5a2a1e79
- TakerPaymentSpent: e6bef2c36e13fe844c096b3f6a10218653e26049686a09c1c06bcd328f08f872
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.