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.
a494823f6d97bd458bdb99612743c1a94bdb3057cb726974bf854a57e59e340d
Both payments are on their chains and locked to the same secret hash 558ef8f501f50f02b71c9fa133af5bcd1e96cbb3, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: a494823f6d97bd458bdb99612743c1a94bdb3057cb726974bf854a57e59e340d
- MakerPaymentSpent: 95bdabc4d816868709c836b04f4a1fecaf2c129a9aeccc139484ff4886d815da
8c50359fe8fb5af5db56f74484480d0cd5205e58037180344cbf390bed5084c6
Both payments are on their chains and locked to the same secret hash 558ef8f501f50f02b71c9fa133af5bcd1e96cbb3, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 52684380a66e705d038651baf4d4cdbdec5923d7c4ab914f7bf9c8545ec6aeb3
- TakerPaymentSent · TakerPaymentReceived: 8c50359fe8fb5af5db56f74484480d0cd5205e58037180344cbf390bed5084c6
- TakerPaymentSpent: ac3f137dfb18c30c293c0779f9ec9b5910ffdf38df749b9f9d62f946ecb6fd01
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.