why2 reasons
mandatedestination_not_allowed
op 0 pays GDTT6QZMZV5BI5Y3WW4AOG4WYGXSTXJQTJXZSGVAGY4LP3MAPNPP64EF, which is not in the allowlist
counterpartycounterparty_denied
GDTT6QZMZV5BI5Y3WW4AOG4WYGXSTXJQTJXZSGVAGY4LP3MAPNPP64EF is on the screening list: you placed this account on the screening list for this run
what it was decided fromfingerprints
- rule compiled from it
- 239bec610bce6b57cce31d5b82509785ddfe6980ac7c691f56205f7500ffb8cd
- request
- 50303983402c2b00085d4f0d4312a3a68a1a94fbaae0afd5911a0e7f19cf320b
- transaction
- 35e044eef74489e1570d362bdfd9fa3964b8f38b0c44ca1b4d957d9c4d05f061computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 68780
the chainentry 68780
- sealed to the entry before
- 142081c91fa93a6aaf63206a7b5dbcfa5aaa7853b171fc5b81d2015685c2d997
- this leaf
- 38589eb6fe6d9729c19b80fd0758d0315b78cd052d604cad8fee62f8d77b1ac4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- atZLlEbaHrMfq3AA9/UMSFUC4o4GmJPKw+sg7xbVHx6trKdJ9NzZ+nTwqBVdsa+7jqHMyD5E6oBiGDd5cKMjDg==