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.
b05ae9d7eafd6c2b7814b820fd23680d3168a84984f0852bd418667331012dba
Both payments are on their chains and locked to the same secret hash dfa0c177e6bf9a0fe5c8d62fd6d1d15818f8662b, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: b05ae9d7eafd6c2b7814b820fd23680d3168a84984f0852bd418667331012dba
- MakerPaymentSpent: 20c624e5951de2f84971d2e96bf32cd05f82e38a08b082e62f4d72e07b921412
cadf1363547fe75f543776b87a4cc6f43abcf3a0717aff5c1b07681989e23247
Both payments are on their chains and locked to the same secret hash dfa0c177e6bf9a0fe5c8d62fd6d1d15818f8662b, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 66fdd88b866d584f4a736db10f490cec541f3a5813698ad2f75a84c603e9c008
- TakerPaymentSent · TakerPaymentReceived: cadf1363547fe75f543776b87a4cc6f43abcf3a0717aff5c1b07681989e23247
- TakerPaymentSpent: ba86ba8f586e31306599c99b785da85abc0ab0674ef89b4a8604c32c202b0525
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.