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.
3e0ba005a7a2d7253820dc3bd956ea16617302671c5c90158d25ec029dfa6c92
Both payments are on their chains and locked to the same secret hash 0f29e4e33d08d037c2ca463a749ff15a9fa4491f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 3e0ba005a7a2d7253820dc3bd956ea16617302671c5c90158d25ec029dfa6c92
- MakerPaymentSpent: b051e2b598ac7f42d5fcbf125e1f2227cd28fc0a89dc6ecc335eec0e92ab689b
5d0e308e1d5a36e62459ac0ad894a3cdc6d6b336df66260a3c25ed7105dbeeca
Both payments are on their chains and locked to the same secret hash 0f29e4e33d08d037c2ca463a749ff15a9fa4491f, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 4342ece01a23d111af5db6332d3c6f6472e25e236eeb9475b01a7f3b4201fb74
- TakerPaymentSent · TakerPaymentReceived: 5d0e308e1d5a36e62459ac0ad894a3cdc6d6b336df66260a3c25ed7105dbeeca
- TakerPaymentSpent: 1639b4a8f4a56aea48978a7c8181ad217634973c8f486cc4d47ddcf83b68bed5
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.