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.
0aafd4f0f324f010ea99997ac221f7282c9830a986cc04abdb4093ad6c1fa358
Both payments are on their chains and locked to the same secret hash bfe3f4f6f6f54e842f5f8aa179b3b5705918adc5, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 0aafd4f0f324f010ea99997ac221f7282c9830a986cc04abdb4093ad6c1fa358
- MakerPaymentSpent: 2478b1c231a0df6303da4db9b93580a4b7161d00dae4843daa0d3b7f0b5b2c1b
853e9c13d27a7c10516d7a6330617246c3beee875229cd60133a384482adf328
Both payments are on their chains and locked to the same secret hash bfe3f4f6f6f54e842f5f8aa179b3b5705918adc5, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: 29c372c49b5afa0174648ac1a741ef28d332ef775561343f8c253b2f923701da
- TakerPaymentReceived · TakerPaymentSent: 853e9c13d27a7c10516d7a6330617246c3beee875229cd60133a384482adf328
- TakerPaymentSpent: e26e87fd4fe68e2b62e8aa06e5173eae4d1bcb36b40f25a24f036392cd4e4ed9
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.