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.
abaaa5bd1bbec2126f5da5c08dc9c949f9ca107d5b85a4f220deb365147f3d98
Both payments are on their chains and locked to the same secret hash 6cfdda4392f068f3cdb16607f86b55c2199dc542, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: abaaa5bd1bbec2126f5da5c08dc9c949f9ca107d5b85a4f220deb365147f3d98
- MakerPaymentSpent: 2538f32ab9da42390ca07e41addb7969d246f6311564b763619babfd08008b48
2340d6fd220dceb44947ef1320d0da6c79ef43b83ed55d9540e3d7bcabe25930
Both payments are on their chains and locked to the same secret hash 6cfdda4392f068f3cdb16607f86b55c2199dc542, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: ea0aae8dc7c89410a1b269d662d2a9cdf9cd4c906a18d14f4de8a118b9b09148
- TakerPaymentSent · TakerPaymentReceived: 2340d6fd220dceb44947ef1320d0da6c79ef43b83ed55d9540e3d7bcabe25930
- TakerPaymentSpent: 7c63419bdcf13169badb21978c60568709ef50077dd3d1f5d580f2907225ff3c
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.