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.
85c8661ac77f4e8c176ce207a35f6a7d55ff14eeb508aa1e447ecbea93715c10
Both payments are on their chains and locked to the same secret hash 8837ae1b4793ee381d0ffa484b312785423e3b52, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 85c8661ac77f4e8c176ce207a35f6a7d55ff14eeb508aa1e447ecbea93715c10
- MakerPaymentSpent: dd53241038f9c5a0807da49123bc19de479952948a7a5ee52b6ffa9999f91825
993cadb37e7b332867f9a1ffd26a03835d0b9bb840027124345d4432522892c3
Both payments are on their chains and locked to the same secret hash 8837ae1b4793ee381d0ffa484b312785423e3b52, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: 8d47aee377139b251d791564f917e2f8cfe5fa46474745da3a94080e6b87cd82
- TakerPaymentReceived · TakerPaymentSent: 993cadb37e7b332867f9a1ffd26a03835d0b9bb840027124345d4432522892c3
- TakerPaymentSpent: 3de9791cb849fd5aac1b06d84d608377296722ff562b16a734a53c0dad4c4ceb
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.