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.
b3b3fe8e5bea88a35a3ed7a1386b521db893904108d48f354c0ccd06f1025e14
Both payments are on their chains and locked to the same secret hash a3c165fec299b509bf8ee0a44e3e179f8a02f2a9, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: b3b3fe8e5bea88a35a3ed7a1386b521db893904108d48f354c0ccd06f1025e14
- MakerPaymentSpent: c471a3ba2f59b27d823e5f7940af5dad06d26404f119782947d4f727914bef38
9fda5dfe67b7ed9e1e6883bf6c04c224ccb66097906042ef1665d089f27c2391
Both payments are on their chains and locked to the same secret hash a3c165fec299b509bf8ee0a44e3e179f8a02f2a9, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 3657e61cd5af4483b76bf6592ccf6f67f969d60994a96e06e719c2b2ee84eb23
- TakerPaymentSent · TakerPaymentReceived: 9fda5dfe67b7ed9e1e6883bf6c04c224ccb66097906042ef1665d089f27c2391
- TakerPaymentSpent: d5d36033769bc74d62676a6cd73f54183ef9b60a8366a50eb4ae07ff422c68b6
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.