why2 reasons
mandatedestination_not_allowed
op 0 pays GC4DMX4FG6DK7DCZANWLIHKXFIQ3ADIEDQL4WVLE4LEZ4HG2RRDUKS4U, which is not in the allowlist
counterpartycounterparty_denied
GC4DMX4FG6DK7DCZANWLIHKXFIQ3ADIEDQL4WVLE4LEZ4HG2RRDUKS4U 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
- 881d8808f6092fe6700a3db9cad580adb2cac038e056515321fd2121356e0ea5
- request
- 3fa1d526debe1699e6d5a3727c8e2dc132a336769b4388f1f182689d00e11176
- transaction
- 042ffbf228b6a7f50ac52e53edcfdb26ed7787b79c9a76d06c084927aa5d4d4dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 36264
the chainentry 36264
- sealed to the entry before
- 9f7f3677c5c1e27c5ac3f7cf0c5a8bd325319b1ece34f94c37e0693920d51c81
- this leaf
- ff550552304a2eb8a21218377c9093f0e21b50caef3bfadd79eb16f2b9209fb2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Yj+/EtE0vQg4ECkmo9QPyXkXCSLy59EeaBdVocofKsKmUYsg6cQ3w6fOcml2OttR+AdGoqqWgUIcIyDzoZPXCg==