why2 reasons
mandatedestination_not_allowed
op 0 pays GDE5R4QSML6TVH3HVCCUJYI4JXOMFPWLTEQTCMRHSME3DJROLEUGOAVD, which is not in the allowlist
counterpartycounterparty_denied
GDE5R4QSML6TVH3HVCCUJYI4JXOMFPWLTEQTCMRHSME3DJROLEUGOAVD 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
- add1c3071fbb694f5684e43ee4def1e58cd42917c333149039cc2774880a7818
- request
- 8b53c72493e74aafcfe069f5db77d2a9f2f4b6a266bb13e32574f197c46d6ddf
- transaction
- 513d4d1eae68cc095557b3d69bd955850ae4f2784b87c1b81a6efa53826f2b32computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 21639
the chainentry 21639
- sealed to the entry before
- 924672bc7c14c62c804b0b58683cc1170cd8272fc021e424543448fb4164a21a
- this leaf
- a91d595ccac157b85f31215a7fbb89fe434fe19fa4df16e695125fc0e1f7ba04
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 5vonE3IZmIfI1T3G16PZeWd9CXtpMdmAs04lQMrDoYniLqPPSpKdXWkJlLnWkCEi+0+SQAc3wni/8qHMg7pcDQ==