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.
907ebf5a2f6c778228993741bef6fd21ad71f206510f6247cd86329e5a7d6fab
Both payments are on their chains and locked to the same secret hash b6d26a60e5d6752de5991e680ed2f32c6135be45, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 907ebf5a2f6c778228993741bef6fd21ad71f206510f6247cd86329e5a7d6fab
- MakerPaymentSpent: 5a0efaecf75aed9e2afd4c1791913001e064e20500a48a91c3ba327fc0adbb8a
738480b670ba375bbfebc4d9614458234a0312b435ea14be633e044fbec02ac5
Both payments are on their chains and locked to the same secret hash b6d26a60e5d6752de5991e680ed2f32c6135be45, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 931424a822affca249075fc47643dfde2cc202878f5233f01ba0e5cef24da57a
- TakerPaymentSent · TakerPaymentReceived: 738480b670ba375bbfebc4d9614458234a0312b435ea14be633e044fbec02ac5
- TakerPaymentSpent: d8c6e6943c196b1e2f2ba47d8972df9593e74a8380077fa3cb269ad1bc13046b
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.