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.
dbd7b6f899e4d5929cecddd423d7034220c515e15153afb8dd628c47a0592866
Both payments are on their chains and locked to the same secret hash 27763039f957591cda4e126ce79875fffd50186f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: dbd7b6f899e4d5929cecddd423d7034220c515e15153afb8dd628c47a0592866
- MakerPaymentSpent: 0bbeba26f8a1b4d8eeb03443d0347fcfa0d492fdd841b8ce2e7582e9c359f549
47176392329af1e194d9b7c85c0ff410c04739c840121d8e6f3403cf14f8df7e
Both payments are on their chains and locked to the same secret hash 27763039f957591cda4e126ce79875fffd50186f, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 17133ec13be5d5335d9df3984ec753cc5825d79e5badde0bc58025765639bbd8
- TakerPaymentSent · TakerPaymentReceived: 47176392329af1e194d9b7c85c0ff410c04739c840121d8e6f3403cf14f8df7e
- TakerPaymentSpent: f1e537fb6dd29f904b05527ea60528fb44c20986ddef422dc58c9883ade86ad3
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.