why2 reasons
mandatedestination_not_allowed
op 0 pays GDEDBQF3JB4H4MZNKQJUFJ7T22PZGPYGSULRPUG22FE4S5VTNI74JUOE, which is not in the allowlist
counterpartycounterparty_denied
GDEDBQF3JB4H4MZNKQJUFJ7T22PZGPYGSULRPUG22FE4S5VTNI74JUOE 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
- 14d4c4a560f147695d49fd07be3f29c4e7258aecbff0ead51c935766ee93bb9f
- request
- f146fe134bd266db074df6639411fc4be14535ce78f0454c1ca0f30df5cf6569
- transaction
- 85139a75d19e81d522ab7419fb8a7f128b3fa569de3e07dfe209d88cbeb9971bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 73216
the chainentry 73216
- sealed to the entry before
- 656270ae9c5936828925e8d311db3405aacbde5a1b54980d3ded529e3e4e6dde
- this leaf
- 95ac8ff520fca9cba33406f4b47a43875fa4773fae64a7d586b3521250185835
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- JB4z2bwHKrs4EfMqNnN9EE2dFbNlr1Jyz2xnL3ZbbIoKRp+J5SdNa9z0nlmq6V5441HCj+WJs+aPStJRH3t/CQ==