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.
093bfbeeef0a7cc64a4e6a9e3d9e84b993cc0e927b7f8d9464b5b7309d662f81
Both payments are on their chains and locked to the same secret hash 6174a53e97024b9e6beb0f61a8d9bb401347a820, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 093bfbeeef0a7cc64a4e6a9e3d9e84b993cc0e927b7f8d9464b5b7309d662f81
- MakerPaymentSpent: bd0f9c5d1ff3aab099ff63ad3ac4082cdc8b10e657c62430f76873eb226a1e69
3716bad9aa1b1743e4e404a35864c5655d140f8de86c4cd6846cc7bc00e2963b
Both payments are on their chains and locked to the same secret hash 6174a53e97024b9e6beb0f61a8d9bb401347a820, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 4442687fcbb7a5301aec0e97dbca94f1f18211eff4478fe6e912f6ac06a15feb
- TakerPaymentSent · TakerPaymentReceived: 3716bad9aa1b1743e4e404a35864c5655d140f8de86c4cd6846cc7bc00e2963b
- TakerPaymentSpent: 8bace20e0f585b15399f5328b6c754af20bb1b7fa36b204a42e5c9e769d80634
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.