why2 reasons
mandatedestination_not_allowed
op 0 pays GCR5B2OUUIOSX4ACCEQKNSEYBGELZDEVNFF2GNMOBFHUEBKBJE7A34DH, which is not in the allowlist
counterpartycounterparty_denied
GCR5B2OUUIOSX4ACCEQKNSEYBGELZDEVNFF2GNMOBFHUEBKBJE7A34DH 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
- 1d88a31c43e13bd5fd895c2120b8844df2a1564cc12a5eb9ef269e0d7955c3c5
- request
- 98ca2a15e58fa1a3860a8a8df2f5d5de8e18509fdbe8789c3e20c82d1ae4573a
- transaction
- 09a15b0cb74b4acd9870e655de442f4f62fd5a614abff98a878ea4be1a126ccecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 31835
the chainentry 31835
- sealed to the entry before
- 65516531bb62e5941d86a3eed1cd95b0021e3689d04cfba424d9af24ae635c9f
- this leaf
- 4d45d54a7308372dd53ab26bd4f7e3b4b34142f3ae5eb82d8893309b3d016794
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- GOPa7twUInLpukoWpGL7VfpJyvaTsBYkPRUuNNm9iTW/a6W2iFSeThGixVQu6DRkm0DNzrKyGK8tCZGp3jXUAg==