why2 reasons
mandatedestination_not_allowed
op 0 pays GDDEQXVBJEYQP34FST2QMH7CES3STDRX2UHJFFOZKHGPSMM6VQBLCA2X, which is not in the allowlist
counterpartycounterparty_denied
GDDEQXVBJEYQP34FST2QMH7CES3STDRX2UHJFFOZKHGPSMM6VQBLCA2X 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
- 5a135e4080ae1a4a2e6df36dc774f45f3c681a1942ec1f54d0c6f3b49af4b58a
- request
- eb54743961ac7d674f2e481c75e7c924d35295a3c5cbf8eec08da65f6d36f96b
- transaction
- ad373c3fffd0cce8432dce5f6ac0b22230d29cd94cc694abcfa84f40841159a4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 76259
the chainentry 76259
- sealed to the entry before
- 5eaaf40dd4f2d9911bcbdc9fabd50f2afec59d00d7a21261ed1618fbabc56e75
- this leaf
- 3ec30c0427cdb60bd0324ee181f42ecf0b6f99f1d7a8245d68b62f79efefc130
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- EEhARsueMZ+bI1FQukV+9FpWT0zWGTcxeUkK7xZ3Pqb3bGYJce6FKrIFsCOWl7H6eqqGhVgBEbFvPBbsCzcSCw==