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.
ca07df7f71e240b691f38ba0e70e42ed9e4fefc3993df124df7b1f02a7125cb8
Both payments are on their chains and locked to the same secret hash e8507a270fbc9e9a2c9d5cf2a96a28947cee2a42, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: ca07df7f71e240b691f38ba0e70e42ed9e4fefc3993df124df7b1f02a7125cb8
- MakerPaymentSpent: 519fab13bbfb56f38788b1e2576e410059d8b552968e9edb94de01239ef90872
dd0bb43e0bdb822820c9e4fa365ba79d304bd1761b659b4b1e4df59abeca0331
Both payments are on their chains and locked to the same secret hash e8507a270fbc9e9a2c9d5cf2a96a28947cee2a42, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 475d7008a69d3fd7f605fdb324f73948b1485e119f77ee4942c51501221a5e70
- TakerPaymentSent · TakerPaymentReceived: dd0bb43e0bdb822820c9e4fa365ba79d304bd1761b659b4b1e4df59abeca0331
- TakerPaymentSpent: ecf3bfe150d367973317a7ee9b0febd7e252aab3dd7491ac667fd4afdb9b5d7c
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.