why2 reasons
mandatedestination_not_allowed
op 0 pays GD3JDWBCCAZGHT23GCRF4TOCFBDO65SLBRWGSCPMEOTWATK7QKBIEVUY, which is not in the allowlist
counterpartycounterparty_denied
GD3JDWBCCAZGHT23GCRF4TOCFBDO65SLBRWGSCPMEOTWATK7QKBIEVUY 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
- 425dfcdda0a63aa38c99829d39e6846ef8282c03fae911d550c6f97c9244b068
- request
- 63be27c712fb370b50f70c7748cac470529d481f06ccf0c2522a5f917c45f6a3
- transaction
- 2fc80b51ef9d60a1666c293d46dc96590bb9857337f75025d8563d6b8af99cfacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 45338
the chainentry 45338
- sealed to the entry before
- 0d7508a945eef2dc009206467fbe5930fddc64794f7331aeea16bf316f9e274c
- this leaf
- 5b57412421f616efe4b2b2b34b0340afbb0d8c3be9dba7aba784b2dc0d3fa5ad
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- EFeEzJSrPu0zzZHStA3pgjPgp5z4Jw/bA8efymC9Njs05lVM+uhm199cSE9tXglNcBIK6CXQ4a7nkypc4t4bBQ==