why2 reasons
mandatedestination_not_allowed
op 0 pays GDMQ4V55CECA6H7V75JXPCXR77LLGG4HO5VSLXFVHA5FV6ZRPQFHLLRP, which is not in the allowlist
counterpartycounterparty_denied
GDMQ4V55CECA6H7V75JXPCXR77LLGG4HO5VSLXFVHA5FV6ZRPQFHLLRP 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
- fc4bba0b9e6f0357ddd491204b6ca77a35bcee461801a134cb84a7b3d7cb1330
- request
- e5a6a85404699036a502a238512f9d1f7d60c81cb04188ca5888f3eb12b712a4
- transaction
- 2eee10e9d7a915e746cad95e6a2a0a0d1e6ba4911f739e96c41699b4b768ce19computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 36155
the chainentry 36155
- sealed to the entry before
- 927501f6ecd3f45c90a448fe2b777c3dfc5c8a301e1c4c042400ca38d59d562f
- this leaf
- b675239e965dc75fee7364dd3af811c4b41503c1c853f228124f12fc2e2a8394
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- eJXnwUggUnY/zGTI0vNRrqLNL3zQbW72OlAWxXwBiyeXJJfuTiJRG62F2OqfyPu7K0p+n9Cr3OlWfInlf2GDAQ==