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.
510c882f4e3de5e7398e2b82fd5452f982631853ea40a6715008d7d16ba37b34
Both payments are on their chains and locked to the same secret hash 0a143f490623a0643f41022b2a98e519c5306b68, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 510c882f4e3de5e7398e2b82fd5452f982631853ea40a6715008d7d16ba37b34
- MakerPaymentSpent: e0e31976cb1e2c834752eb41686bd00dda90c7af9c223a8f2629db67e138a8fa
3211ce89cd0b8ab2d20f9bdb313aa885bf0cfaa9b0cabd66fb3df323f4846b99
Both payments are on their chains and locked to the same secret hash 0a143f490623a0643f41022b2a98e519c5306b68, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 27851a2e7caab28b952f461979b4c10ff3dbb0e6e6c832c5cb05cb5082c9b5d5
- TakerPaymentSent · TakerPaymentReceived: 3211ce89cd0b8ab2d20f9bdb313aa885bf0cfaa9b0cabd66fb3df323f4846b99
- TakerPaymentSpent: 092d01d67d7f9c47bc1bcf00f006a7ef63fd680ada11016f9fe088e94463b607
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.