why2 reasons
mandatedestination_not_allowed
op 0 pays GD64KIBH4ZX5YXPHGX47NP77QQP6QSJMRZYOM6ZJ73DQI2LKCNQIOZTS, which is not in the allowlist
counterpartycounterparty_denied
GD64KIBH4ZX5YXPHGX47NP77QQP6QSJMRZYOM6ZJ73DQI2LKCNQIOZTS 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
- 22655e0e3dc8395cdeba1c7e089cbc33bf8bda69cc70a2d8dd7f1871b6700a35
- request
- 30b5e27292e11929958f41e56ad0b9f0e0c4566cbd38028f64fb17e8fc170ecd
- transaction
- c31d420c37c0e9cc75956e3b064aa5315f7b4f53c2000c70093fed8ec0013daacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 68821
the chainentry 68821
- sealed to the entry before
- 3bf66904402a225d0c820d530a27fbebef353bce72a5a543bd85d8ef407ef8e7
- this leaf
- 09a122ae3f3680d5bfc50019db381bd255057e1f34470d87912ad4b205b2b22c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Jlvu0M699DILDQRJD+t5omdc46JKxa2KJY1gBLvpio2tHwgHv7PKwgq2DGx2lseCYN7V+64Cc4Cb3LdDthK7Cw==