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.
dfcfb1b0d39b54e1129dfeb0a8447026b991f67a41343d4d535e3173171acb72
Both payments are on their chains and locked to the same secret hash 96260153e23e5e9fbe732410e2aaada7ed28bb3d, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: dfcfb1b0d39b54e1129dfeb0a8447026b991f67a41343d4d535e3173171acb72
- MakerPaymentSpent: d9aa02138850ca294643c3989e56b073acd0155f08ed972d9112c61e3f586f3e
6c4b49b6e4b55eb28acd57de99a0f23641d8be092fc88d4d51e72eeba4bda2eb
Both payments are on their chains and locked to the same secret hash 96260153e23e5e9fbe732410e2aaada7ed28bb3d, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 24b14b26e76aa152ab0dcfacc512212459d27b4c4325b29f75bc4a2e2dad0278
- TakerPaymentSent · TakerPaymentReceived: 6c4b49b6e4b55eb28acd57de99a0f23641d8be092fc88d4d51e72eeba4bda2eb
- TakerPaymentSpent: 6cfe0652da56c6584efd13054c0d0228800f1a7b9ccbf2cf64294eec3a80d2b5
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.