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.
a85127e5fe4c583e55469cc01fd4745d32f0fb248483277da41a6afefb38a7cd
Both payments are on their chains and locked to the same secret hash 508695900748f55d85af4884ab9e29e7f2cab438, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: a85127e5fe4c583e55469cc01fd4745d32f0fb248483277da41a6afefb38a7cd
- MakerPaymentSpent: b81b2a4b72ba87bf3d93508422bec8ba7d86d1298ecc3b006868ab2221377abb
3d57db4c3afc4af4faeb261907449707f2adea8dc8114affade15e8b0a24a535
Both payments are on their chains and locked to the same secret hash 508695900748f55d85af4884ab9e29e7f2cab438, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 35e9dda657c6b3425769d8ab19c1f26647180a4ba51a0b0e7d904353468805ef
- TakerPaymentSent · TakerPaymentReceived: 3d57db4c3afc4af4faeb261907449707f2adea8dc8114affade15e8b0a24a535
- TakerPaymentSpent: dc827874c2c12192691c71b370e20ec44851990069328484eab4d4af599c86c4
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.