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.
8523b3f783354a14b222ad0a6e491806afeb2463d49dddd69e22b11b180951f2
Both payments are on their chains and locked to the same secret hash 29063441ca548435cc232e3d55c6867fb8326906, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 8523b3f783354a14b222ad0a6e491806afeb2463d49dddd69e22b11b180951f2
- MakerPaymentSpent: 21743be191cd9fec960c0ee097ca9fcc4af055e10722f33f0286dfd434e9d22c
5f6a7249b9c5337c8177ac58495b580fe5b3ec82df07dfe7ae8314ca204cceac
Both payments are on their chains and locked to the same secret hash 29063441ca548435cc232e3d55c6867fb8326906, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 687074fcc789bb7946b5dd913c633a86ee9001b805e2dd4a447a481ed0b7df1c
- TakerPaymentSent · TakerPaymentReceived: 5f6a7249b9c5337c8177ac58495b580fe5b3ec82df07dfe7ae8314ca204cceac
- TakerPaymentSpent: bb1963a8595fb7678446502c7125ab46a94410d33e4680e50f4b0ffd23dacd62
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.