why2 reasons
mandatedestination_not_allowed
op 0 pays GBKH3POLOADPFVOW2QL6YH52QFCORKN7HBQQZSIHKDBUOJOY3ZJOEH2Z, which is not in the allowlist
counterpartycounterparty_denied
GBKH3POLOADPFVOW2QL6YH52QFCORKN7HBQQZSIHKDBUOJOY3ZJOEH2Z 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
- d7f3456f5b6d52b538c18f0907b62c1cb4d8ab0fb6d90ecca6c213833b7ef19c
- request
- f9956335f45b767ca1e4a31bed21ed2293c81e2810a837faab8c2403d4db07cb
- transaction
- 313894040aaa32231a9f535dbdc9afc0d4123135fa04d3d1dd0ead6cca754f14computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 37310
the chainentry 37310
- sealed to the entry before
- a2604e2e8c9b281f423f064820dd623358aae55853397db83de2f7435caf4bc6
- this leaf
- 31ddd3a915d76bd8debcc1abbee64677bcba0e48ede84ce9bdc7874294b305bf
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Deczn4lUc1/AmU5ccKqOYqN6iJ1HFSnMCAcFImRWxbwmC169RmmQcUfBIA2D4yAn0FuVy0FYF6WNrcAhIianCg==