why2 reasons
mandatedestination_not_allowed
op 0 pays GDEUBK2SRVZAD3SXOOGZXTCWZNTXIZCY37Y3LJBGN652NI5BD5JTCLR3, which is not in the allowlist
counterpartycounterparty_denied
GDEUBK2SRVZAD3SXOOGZXTCWZNTXIZCY37Y3LJBGN652NI5BD5JTCLR3 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
- 030fc02ef53f2cc54fd16bc2b4213a54b0e2a4f1dec5eade743a73cb4158ae58
- request
- 1f234e3f6c1de11c35e56cbfaa1f7382df2a9759b59619475d8d38ea6592045b
- transaction
- 23de90a15d0d8b0897c35f55c72f3a2c282e23a5db6649ee0f755b5dc27ec080computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 11144
the chainentry 11144
- sealed to the entry before
- 199a6fa29d2c92fe2e61ddac7a20531e088b6e113269236591b764181bbd6b8b
- this leaf
- c2d3ef1985438c048edcdac1aa2a519c04472ec47a6c3b9f8fcf7b4ef206c0d8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- W7yP3G1WtK+V688D6g9oFE6LfAa7AeUhDFekxEZ7RaXvqM7keW4vsR18P3GIlD3tiKMY95sdjMDcRqh7qgVcAA==