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.
b3dbe0a70624c7041abb91d3319909f26c7cce47932530ac56cd0f8b75a363ec
Both payments are on their chains and locked to the same secret hash 416b94b1c031efbcee6f7bd0a2745ceb555542e0, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: b3dbe0a70624c7041abb91d3319909f26c7cce47932530ac56cd0f8b75a363ec
- MakerPaymentSpent: 5bc91b520c4414210c438bcf9e7e0dcd11cc3570a9e7816ad653de0c83833b7a
2532fa986d19fb6357ef6c8b390a5ddf26217798277f2adc28d932a7e88e1934
Both payments are on their chains and locked to the same secret hash 416b94b1c031efbcee6f7bd0a2745ceb555542e0, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: f4628b60239f2100bf97f02d8639c62cfdfde13079d03ec2c952c23316f0a814
- TakerPaymentSent · TakerPaymentReceived: 2532fa986d19fb6357ef6c8b390a5ddf26217798277f2adc28d932a7e88e1934
- TakerPaymentSpent: fdf2adc57883cbc31426bba383e5369ffe8041da9430106a444a212233162ffc
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.