why2 reasons
mandatedestination_not_allowed
op 0 pays GDRCYZU3EYZDHZDPIC6PIUOE2W7RBGH6MNYIZX2AAF6L4A5XSKE24RKE, which is not in the allowlist
counterpartycounterparty_denied
GDRCYZU3EYZDHZDPIC6PIUOE2W7RBGH6MNYIZX2AAF6L4A5XSKE24RKE 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
- 4d58b6cf18bcc0e4186e28dd60727440a50123b932bfa71174e24e8f91c8c6b2
- request
- fd0df20fc251f3a1dfaee4bd0b29dc97b77c9092a29a672cadb8e86cd2762795
- transaction
- f2d466f9ff897a0e4b7f5fb552e7856a629bb9c1c778ff57448babbfe6a4ec7ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 15937
the chainentry 15937
- sealed to the entry before
- f1983e2889dd7ace1c811d661531a965387ca2eb986f6fcb055682b1d8fb5ffd
- this leaf
- d21339c1ae53929bdf752a94a2066fc35635204dd3d2cdda0e6ff6c055e0f198
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- zbgSmtsiaJ+i5Ffh+diJ8feA1vnVJuQ2AjIUcTZyznSq9h1wBj3LpOA8ai6C9W0iMQv1Qs0602lMG2K38SEFDw==