why2 reasons
mandatedestination_not_allowed
op 0 pays GCPTM3FMGWNMS7DNQYFFC3LTPM7BPXJ5LSTIVDF3ADNQDBXQDI3RP37S, which is not in the allowlist
counterpartycounterparty_denied
GCPTM3FMGWNMS7DNQYFFC3LTPM7BPXJ5LSTIVDF3ADNQDBXQDI3RP37S 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
- b01b73612de01f7ea0b928a99ebe9b6bb667d009ca0f80324b0b2b006547e98e
- request
- 6b24b9c8685e56230a014dbf129b6a1bec653f2bd2e2565710e94338d26454b4
- transaction
- 2a5aa6c01694e1492f75842bf2402dc4342c283d06bf023575c7f1a78297368ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 73269
the chainentry 73269
- sealed to the entry before
- e10d2226432df17829f39531727b2f60eaef6af999956ce87896fca353bcb88c
- this leaf
- b0658dcb4fc1d01c3619050e870ea75d247f5679377b672a218d1389cbdec7cd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- YbTZzvoEGAoTSSBzGhKoWlsBBUqofoXBPhntpALooMGfZvny+ER0pPxq7H8wN2i7DHaKIv4elMnBpbXqIFiOAg==