why2 reasons
mandatedestination_not_allowed
op 0 pays GBUS5H7T4L72MHCX5XC7Z2AAVYNYEKKE7U5MY3UUNRAP5ENQYX4LUKDE, which is not in the allowlist
counterpartycounterparty_denied
GBUS5H7T4L72MHCX5XC7Z2AAVYNYEKKE7U5MY3UUNRAP5ENQYX4LUKDE 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
- 753f1f8da2dbcaaffd74a2ef1d75e72375c4d20a917ce1fe618f9a8b2e2241d6
- request
- 97af411e9f0dc74cd0d6b16b73d94ff0e8d9b29c328729a3cdf1c5de5835c4e2
- transaction
- 91ff0b747fb694820088b70dadcc812c55c876638091338de1741652aec63a51computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1014
the chainentry 1014
- sealed to the entry before
- b91c6dd87235646ff8ca535b3beff0aee50c95bad9efa37a6fde632608bc6e28
- this leaf
- 44743403471ff355a85fc17cd8a2179cad7167d2518af668998bcd9fcaa16c37
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- HkC3DGmc+TQCcdEf+tQiXSNsqvf7RE2grn9w6mHdWiiu5aJmHncStT+0amu6/sBxXjhMoOH1kHqD1Ci/jYjLBw==