why2 reasons
mandatedestination_not_allowed
op 0 pays GDBJQQPPP6AC3NDPXYWVM63FN7BQQAAB6XDS273R7CQX2UAH4CZFMPW6, which is not in the allowlist
counterpartycounterparty_denied
GDBJQQPPP6AC3NDPXYWVM63FN7BQQAAB6XDS273R7CQX2UAH4CZFMPW6 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
- f1aef14e7b5cd16035c91ff8f168cc84609078a95b126a35306fd66edf99e083
- request
- e96bd1f02e0e0ed35df1c30d9de48a879e72c636c92fafb45fe48209a330c082
- transaction
- 602152b9f57c58a390709b4cd1aa2a8e4ac72c64b2f382d9cd52efdc11d60649computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 10038
the chainentry 10038
- sealed to the entry before
- 6277440f027ff5e60b17089c71490046c332af80208264a9be9020f159b9cc71
- this leaf
- 8a7130f0b20208e94c8b56f85567ce1ed940265338a96575e8db4f020f98d4f4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- dYwmakdAvn5NhayWsuySub4bPVlHorzbU8ZhT2MZAwb0VYR7E9gI/EmV1wf5c9+dla3cmu5kEBLegpHu0WSaBQ==