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.
2c26bd424cbfc1aee6d3c6ee46873b7748f341dbd4d98c2f40b9c0590e7fc5bf
Both payments are on their chains and locked to the same secret hash ddb8daf28e4b54e6f9fd3ad638a41d8dd0130a5e, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 2c26bd424cbfc1aee6d3c6ee46873b7748f341dbd4d98c2f40b9c0590e7fc5bf
- MakerPaymentSpent: 4544f2dab651d8954bfb2068194e5a737aa09efc9a134ba74109bb6bef76cefe
2526f8a1eca2825ecf45180c4ebb77debed0ddfa21d730f11cc3ce519e0e0b19
Both payments are on their chains and locked to the same secret hash ddb8daf28e4b54e6f9fd3ad638a41d8dd0130a5e, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 74b1b4ba86e840b9a873b1fd86373da369cac2117c759d852102ab867acdcf7b
- TakerPaymentSent · TakerPaymentReceived: 2526f8a1eca2825ecf45180c4ebb77debed0ddfa21d730f11cc3ce519e0e0b19
- TakerPaymentSpent: 1d3db7bc1b9fe1ecbf688c16d0d452bfe9f702448d27920b47efa9510ca0d53a
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.