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.
6934180033bd3a09ed3d20e4913759fe511f451a4bfc7f19b584fd917513675b
Both payments are on their chains and locked to the same secret hash 2dc89e6619fc08381218b563d69e80d0149abe7a, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 6934180033bd3a09ed3d20e4913759fe511f451a4bfc7f19b584fd917513675b
- MakerPaymentSpent: a21ac6139d43d23e7c88de17e19439196b1b1e79b66753f660fb0af0f18e83f1
ee566de8b08c03ac88a1aa5210148e81f16197afe9af6a36710e3d3e284debe8
Both payments are on their chains and locked to the same secret hash 2dc89e6619fc08381218b563d69e80d0149abe7a, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: e698eac7e806a7a59b5bec729ff5a507a872872ba9113bc018233beae0dbb141
- TakerPaymentSent · TakerPaymentReceived: ee566de8b08c03ac88a1aa5210148e81f16197afe9af6a36710e3d3e284debe8
- TakerPaymentSpent: 38935f9b18909f025b93b00aed4bb50a9d5ea69ec468be78439a1505078c11ed
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.