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.
1ce8dbd0b45e19a320c46e09eb23705f77e81de044c8c98edc9aff6bf766c61c
Both payments are on their chains and locked to the same secret hash 2633c090b40975e0cb78d4cf82bffeddbcd32eb9, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 1ce8dbd0b45e19a320c46e09eb23705f77e81de044c8c98edc9aff6bf766c61c
- MakerPaymentSpent: 4a37d47334aaef97a88279731fd74a87c8fa8140c34e99b927774150a11fa645
069308dbd25b42dab19b2a53301d5259086ce2f9f5a042cf2b028949cfbd1345
Both payments are on their chains and locked to the same secret hash 2633c090b40975e0cb78d4cf82bffeddbcd32eb9, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: a564bb97a976c92df7636bfddac23e0b7f48dcd81dd29a64eab589faa32f2de3
- TakerPaymentSent · TakerPaymentReceived: 069308dbd25b42dab19b2a53301d5259086ce2f9f5a042cf2b028949cfbd1345
- TakerPaymentSpent: 285cdfcfbd08d713c4232b0ef345ad244178c57ab82979a473f028b619ef883e
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.