why2 reasons
mandatedestination_not_allowed
op 0 pays GDILKZGDXJ263U7YDJPMZWHBBEDYXP6TWYDXEARGCEA67WYBXGOZPU3N, which is not in the allowlist
counterpartycounterparty_denied
GDILKZGDXJ263U7YDJPMZWHBBEDYXP6TWYDXEARGCEA67WYBXGOZPU3N 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
- 5ffcff54e493f030f0955f9b651d248b92fcab0fd8edd8b921140550a834960c
- request
- 6f12cf4d4f4c70a0c6b29920e1679f6a2b12871d157bd1611f0c3695f7b6942d
- transaction
- 563af379dfb5a56b84719753d344cb7a45949adb33c794f342a7ceecf11e59b9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 25585
the chainentry 25585
- sealed to the entry before
- 8c3ff7bac2dcc38eecad5257272a9da04001dda1c6e4786ab391888ba522d608
- this leaf
- 6e7bdcee9090cf7933337fb1bd41294323e287f6b0ae62da9da2ad6551071179
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- U8DJ1T7TwY90ukjkUxJ/0fPpRtxwruI2ixGuVAvt+R09osAqpHWYT2Ambvl1NP1B5K4l5UGAHW8Gy71jGiiEDA==