why2 reasons
mandatedestination_not_allowed
op 0 pays GDQPORULRGB2FAO74EYDWYU7GRU3BCAHA7YRYERN3LKGHQK2IFJVSQBI, which is not in the allowlist
counterpartycounterparty_denied
GDQPORULRGB2FAO74EYDWYU7GRU3BCAHA7YRYERN3LKGHQK2IFJVSQBI 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
- 774fe5164c969212f9bcbf759c385f23c52d85a98cb7820768a47f98326ec629
- request
- 22af7826bb59136cf6e6c14fc21966c624ee4a523034fbb915d81157e6dd7d69
- transaction
- 12f8a18d92ec3b65735c70a139693ea3cceb47e0a7c595d5f7ac5a5fb6b78993computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 41011
the chainentry 41011
- sealed to the entry before
- a75657b5412c0de2ae2ea95dd6696ee6c1b76a57efe35f577e93bd81d5ec149e
- this leaf
- afe7084494b64d93b98baecb1f0b25f6d07c8b57985b40f92fa69f715a0d30c8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- wqcoy+e6xdquxo6u6ixFbczxzxAr1N+6hlPgBDMUC6euv2cTsCnNMeaeCXA21PjSGYty3KyxR55cRx/nBul+Bw==