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.
3cf2ac6f7ed0e90fdd6d0d7fcbe9b3d3e9b806ce0bd92499ff05abb66776bcc9
Both payments are on their chains and locked to the same secret hash e197ae67a573c122d818735b089b5c748a0b279e, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 3cf2ac6f7ed0e90fdd6d0d7fcbe9b3d3e9b806ce0bd92499ff05abb66776bcc9
- MakerPaymentSpent: fe0c50136832d2b053b16687860ab1f63ebb620263df888e3cf0a6fd43d3e53e
60468679313eac26828b0f5cab81c0a9a1877b2a96849cba23c8140de33b7715
Both payments are on their chains and locked to the same secret hash e197ae67a573c122d818735b089b5c748a0b279e, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 61d21533b1db3077d3788bd887282730f82b29ae35d4e516f9c8fcc19aca44b9
- TakerPaymentSent · TakerPaymentReceived: 60468679313eac26828b0f5cab81c0a9a1877b2a96849cba23c8140de33b7715
- TakerPaymentSpent: 97f73912dff5b271446ddfb657bbf20942c2b8a5bf4b212792b9c53b95569da3
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.