why2 reasons
mandatedestination_not_allowed
op 0 pays GD3U53X23BLM2JYSUG7V5IFTLEUV5UG4LUN3VHTJ2A5XFHHOBXXVFY57, which is not in the allowlist
counterpartycounterparty_denied
GD3U53X23BLM2JYSUG7V5IFTLEUV5UG4LUN3VHTJ2A5XFHHOBXXVFY57 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
- f932bf22afe4d71c044ac26995b45465e756924ca2dfe503c43db5ec9ab5093d
- request
- 0c3641d9cfb9782304af932825347460dddfc96eb259a3433995ddb963e9dd34
- transaction
- 9086c0c80c1bf1cf8dacf9c840039d738faaba6581eb4e18741a7085d209ca54computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 29789
the chainentry 29789
- sealed to the entry before
- bdc347fa880b75b42ed26b62fad2461e47d9472f5101ebfae8419479bde18a8f
- this leaf
- e1a2b19e6c30d9b7ce4340ae01fa63faad171100ba958ebe814a7bd69d704fcd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- iJV+5nk5lfsF3QbpU26F/Uk0m5E4G2LU9tFB+ICyp+nCX4jBYW7pwLrFxgN/1mDG/8OR0rkp5EpUPYiUaKHYDQ==