why2 reasons
mandatedestination_not_allowed
op 0 pays GDTHWOIDX4MH67CQQ5EUNELJYNXDTTEFE5U254ETDZJKZ5JCUUYLJ33M, which is not in the allowlist
counterpartycounterparty_denied
GDTHWOIDX4MH67CQQ5EUNELJYNXDTTEFE5U254ETDZJKZ5JCUUYLJ33M 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
- 28ca80613aea7fbdee45efcc799adc0cd9a736ab8e99776ba37b820da0ca323f
- request
- 7c58f9ab4569e5f6116c64b519957d25b824280fd044a2c62bc98f688f44712c
- transaction
- 6df024130cdfdf2473e1edd6b905f37ed7983d9f2318593d43aa080f15d4b44bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20401
the chainentry 20401
- sealed to the entry before
- 17a9ac61b7e6a3a3adbe3336bc6bf83c59ff1634e570a5562f18ee599f7ba3ec
- this leaf
- 83aad1567c3a63eacebfd997dc2c41e50a1d88cd77025073ca31bbfed09e8eb1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- vl6eio5+Y+qDQYqMaOAsY3794B34CiBYDYGfiu6coR4VRSkbRJkJAWeBlB8anSKd4rM43pu+Yy/pX0K6pdi9DQ==