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.
00e9f7376247b0aea1c4310e93cee5374b32f55f2b660c726601950063cb86b6
Both payments are on their chains and locked to the same secret hash f5fce82c8b6b3d16f427bb86df21eaf1ddc58a34, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 00e9f7376247b0aea1c4310e93cee5374b32f55f2b660c726601950063cb86b6
- MakerPaymentSpent: 4e3b9ba7ceacb0e660fbe9ed101829b7f04abc849768f7f89a510fb218ff6dad
2b7c8694e59038dea5e994a05d0473654b6c66c31d1a88bdca7870543f22bb24
Both payments are on their chains and locked to the same secret hash f5fce82c8b6b3d16f427bb86df21eaf1ddc58a34, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 16afcb144daa975c35d9681a6ec8db5b6a5ab252edf7bd339991be87f4a0d6af
- TakerPaymentSent · TakerPaymentReceived: 2b7c8694e59038dea5e994a05d0473654b6c66c31d1a88bdca7870543f22bb24
- TakerPaymentSpent: a77e1faa4459d9654f8f247bf235e3a6495dcedbe956d0d421c309ac4934ff98
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.