why2 reasons
mandatedestination_not_allowed
op 0 pays GBILB5D5IUH4NNKZF5ZJ5W5IUBCU7ILNWRBTPVDD3JQD5DZ7ABYWR5BN, which is not in the allowlist
counterpartycounterparty_denied
GBILB5D5IUH4NNKZF5ZJ5W5IUBCU7ILNWRBTPVDD3JQD5DZ7ABYWR5BN 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
- f358c05115ac69ee8920827a0a45131cf4282ef3705e3e022aaf797d3e4e89c4
- request
- 55cf547c057483afaf1b5190f28008429f38127fca4e2e144d0be67d278fe482
- transaction
- 11c02b612818d61e0579ef1d9adae3163913eebce8784d5f867e00c8860e21f6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2121
the chainentry 2121
- sealed to the entry before
- 34c449730699f27d594355a78736dcc5de22fa427823185bee8dfd82183c0dc7
- this leaf
- d6b6a9aa32c0d3f09c604651759502df15f8ff9ccf8fa7fdd72c071536092175
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- XVYcgP5mMr374hOamc+Reiq6BO2D2URZwVg2DddSd/MtkizpVaMv5X4ATM6BImmesAFmM2siPVEqpjMj03lwAg==