why2 reasons
mandatedestination_not_allowed
op 0 pays GD2JSBJ3TYEI2WTKCCWKPVSSKAPUDVFXRL64C3BDQEWWMULY2NTUIBQP, which is not in the allowlist
counterpartycounterparty_denied
GD2JSBJ3TYEI2WTKCCWKPVSSKAPUDVFXRL64C3BDQEWWMULY2NTUIBQP 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
- 7b681ae0f3106453e7e54f486ba732d5e994c1f36d4cfe996097e69b2218d3e7
- request
- 3887140bbc6c3db439d6925752a07bec47a8be791467b1a6d5f99087a127c096
- transaction
- 45ebd2c34eee3b1b0e2f54186c0f00cc2292a6184ed57f288410f7337f330f85computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1791
the chainentry 1791
- sealed to the entry before
- ab468c92c1b1bd5c92b523c00f019213d7e6eaf2db1c461b169dc868a9822952
- this leaf
- d5f775105f81f2fa8a0798cca68d0910dd57b547e8b3278897d1f3466627329c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- dLC2eEAz7l2jROyEXmDkygcWO8jUApabljD0J7W7w8EWfHnuQ6VrbL54kXDu0efE/XOLqn0acOqM+9LUPD0jCA==