why2 reasons
mandatedestination_not_allowed
op 0 pays GDEMXKSRH3ZCYM7F4QX2LXZ4I77JVYWM2ZZJHKNDT3YE5YR2JXOSHPEB, which is not in the allowlist
counterpartycounterparty_denied
GDEMXKSRH3ZCYM7F4QX2LXZ4I77JVYWM2ZZJHKNDT3YE5YR2JXOSHPEB 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
- 3c3f4bf59f88974d245778e833548ee476c8f63f05c15d85afc993315f85cb46
- request
- 954566f9d9bf1b17f2500ed2af26115d05c7c6e345456b56b93a6bfd096029fe
- transaction
- da53ea96c7296d76e160291f10c28579243686758c72c3c5f91357c65574aff4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 64322
the chainentry 64322
- sealed to the entry before
- 543605388895b6b8d365c44932d30bf67d09c4c5d225ffb26f3dfb5fb3e37c31
- this leaf
- 56608c8643da10b9252733454b0eddd6f1666f42e52bc88c9f69a2dd9d1d0050
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Lo2dIgh8pU/X123eH+SdboLvTTjKOIbsbrSCGakCXBAF0OoLO0yyP98Ks9Fuws+TtsBVo6Htu0RxFJL2dx6jDA==