why2 reasons
mandatedestination_not_allowed
op 0 pays GBN3GNL7GQRONXJN2C5RKOHWDLKWXZWGHG34O5GPDUIO6KEUJ6Q4Y5LN, which is not in the allowlist
counterpartycounterparty_denied
GBN3GNL7GQRONXJN2C5RKOHWDLKWXZWGHG34O5GPDUIO6KEUJ6Q4Y5LN 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
- e901db65756a4d27e1624fc1b3c22c9413745391cdb857e89c949311c2a37ccc
- request
- 5e06b7c697468147a154e5cd858e550dee6823243a97092dd65f201498a70576
- transaction
- 7bba714a3ccce441de58941d55e2c1382c6f69f6bb841c0c86ae63f7f2c121eecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 77622
the chainentry 77622
- sealed to the entry before
- df032c64ee516e563ba42d483ab3f55699ba72a07f0dc1c77cd89500fcb9c96f
- this leaf
- ff86ddaff5ecbe756fa4dd81dcfd5829ef560ec0cdc4efbc9ee758ddf8291272
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 30AkBN1lEO1c3jQXmm48plvBfLJkJYHabDu07taiE661M52DtoQKY8tyXGOCem9fy/XmQiSuTgQPZSDXnkh3AQ==