why2 reasons
mandatedestination_not_allowed
op 0 pays GD52OV3FVS3OSCZSYCFXERRQNSSETOXSDFURMJJOBAPW7Y6LNUUHZW34, which is not in the allowlist
counterpartycounterparty_denied
GD52OV3FVS3OSCZSYCFXERRQNSSETOXSDFURMJJOBAPW7Y6LNUUHZW34 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
- b63059037e80e7d5e924b14bb330ce630ce89f580da2b59a7205f0b0448eb1ef
- request
- 58fb4bd1d419fca7d3f58f63ef66c12faa956e3f2578c673ffeac2ea3338f21f
- transaction
- a7ef10437b1a8dd583e9a3428bc4b83284274304c265af88e64ac69186949330computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 66731
the chainentry 66731
- sealed to the entry before
- bec33b8f2f00df0109d38c5697a93f59e6bcd9a3a66668ab38c9f3b5c75dd210
- this leaf
- 102ffed59f268d59a7c961bd9c1da2715dc86a49efededff91cf80dd6c3b41e1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- WYrUGyIpwsd/JA3EWwJmUUmgKwI4LxjceTPQSN1sSJH+gRaaZ2ByTQPx8mzdlnNDXyI16pGe4T0XSuL6IOrlAA==