why2 reasons
mandatedestination_not_allowed
op 0 pays GDN4S7CAU7CV7FNLORP76BZ3HWFZO5FUKPXW4RV7VL6H36YRDWAX4MWX, which is not in the allowlist
counterpartycounterparty_denied
GDN4S7CAU7CV7FNLORP76BZ3HWFZO5FUKPXW4RV7VL6H36YRDWAX4MWX 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
- ad05e37282256f514d074888a8d67fd8d7a09239a84ce07f9d765fbc591da43c
- request
- 864d0f296413c56a956a3f7cf58885b8367c8bbd6f8bca9575ef5dcc9ac04f60
- transaction
- 87ed3947e8d80371c192e9bc59131a8dd22a9552df132dd67e6f8371becd2ecdcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 65586
the chainentry 65586
- sealed to the entry before
- ba669ec84102da3cd68f1a1f3bf76b9005c0b6d92a2d32208acf1a9391ebe74b
- this leaf
- ef96c76e620b023f055b3c09791a67d867c9b01944a36f1bf78c93b09f999471
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- WZvs93Ks3IafOEjVwtwEW4rcczNpr1l27ibC4H+3L/i838W8IAWoWU9iuiRVWR77jPa7oHKFPGM1q7AGOouPAA==