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.
b59f702f130f73639c20f441645a28ae147d681d9d0808c0565efb9ef98d7595
Both payments are on their chains and locked to the same secret hash 7c0edfda63ed6e39e1c8b30ab773392bb28b004a, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: b59f702f130f73639c20f441645a28ae147d681d9d0808c0565efb9ef98d7595
- MakerPaymentSpent: 598ab838178efcb8ef6ee285e89ee9a02a683c06938c96071b61cecf90074090
448c560dd29aafe55146e3cd2a0147857dc67f625a43c5dc1804b6a289cfa8ec
Both payments are on their chains and locked to the same secret hash 7c0edfda63ed6e39e1c8b30ab773392bb28b004a, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 8773295fb3708e79ef1ffe8f88a09ae6114811db8f738fb4fd702d606f446fb7
- TakerPaymentSent · TakerPaymentReceived: 448c560dd29aafe55146e3cd2a0147857dc67f625a43c5dc1804b6a289cfa8ec
- TakerPaymentSpent: e861dc901f4241b3242356576a64ba1060c88de53e48a0baecb731227f8d41f4
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.