why2 reasons
mandatedestination_not_allowed
op 0 pays GDGKXMVU56XFZ7UOLKIDKXTCVQ4LTQYFXSU2M7H4BBXFJBRXPD7ZZG2O, which is not in the allowlist
counterpartycounterparty_denied
GDGKXMVU56XFZ7UOLKIDKXTCVQ4LTQYFXSU2M7H4BBXFJBRXPD7ZZG2O 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
- da311cfd02fbb180b5cb3f42d00f987ec05ce06a69e3d7edbcdf28b45707144c
- request
- d22bb6e9ee360a328b4333b4b0866c181816106427c488d27f9c107e0edf89d0
- transaction
- 8b5e75110510ebfa8b772fc7d2ffbf2fddd3d601210f6a9e44b1b4563f588e85computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 6979
the chainentry 6979
- sealed to the entry before
- a928b00b40c242d14f957c7a0a5dd866ec5933146c15785e268678bfdb8cb0a3
- this leaf
- 61e607011f739c003ae0daab68f931408740ef50024e3cb99f0f4aacfda2f01d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- f3tUMVobEiWQtDUykb1yFjm3iqju8tAsjgRv05xeCOQHQq8S1Hat4s9JYH0qV6pvc2FX+HgHD+kWuMxaQpvSAQ==