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.
b95c73f609711be75308bb5880c692b1472ce2a8d764b305c54e8617ca114c72
Both payments are on their chains and locked to the same secret hash 9fd1fab28dc946f67e4274d678884bc3274cde09, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: b95c73f609711be75308bb5880c692b1472ce2a8d764b305c54e8617ca114c72
- MakerPaymentSpent: 27c077de583726cb88b1391ef602a9cd8043bb5c50032eedc17c4283a9d42eb6
87242761834891fde4a0637fea2ff3e5943be9210aa2ea5c70abb48eddda961c
Both payments are on their chains and locked to the same secret hash 9fd1fab28dc946f67e4274d678884bc3274cde09, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: d32680d4cd61c988da9f51b83cbb09cbd0e65e4037428efbb295ed5ecbbd0a67
- TakerPaymentSent · TakerPaymentReceived: 87242761834891fde4a0637fea2ff3e5943be9210aa2ea5c70abb48eddda961c
- TakerPaymentSpent: 942181febad3afa7b78906aac9e3500bf47cf4ea81d25414becf08cce55f6eb9
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.