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.
e4046051a3993b54fd6e27103183e5809b7536066584ff3b954ab57ccc1a452e
Both payments are on their chains and locked to the same secret hash 462849260f99c13c64a0fba9724b5dc561f195cd, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: e4046051a3993b54fd6e27103183e5809b7536066584ff3b954ab57ccc1a452e
- MakerPaymentSpent: 434f4b091d62741aa29146e0db3c958cc565bb01754d0d22caee86434a095151
7d9534c6687e23f48ce4fda2415d6fa0816ffbede23916528de99efc1a429e06
Both payments are on their chains and locked to the same secret hash 462849260f99c13c64a0fba9724b5dc561f195cd, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 8588a7554f5733882fa114040ab7e3c369ac6e0e02bae276810669cec535d32c
- TakerPaymentSent · TakerPaymentReceived: 7d9534c6687e23f48ce4fda2415d6fa0816ffbede23916528de99efc1a429e06
- TakerPaymentSpent: 788621500071f50b09a06b0d74f8175519b3b010594cae8ef9a0b68e4e9b8978
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.