why2 reasons
mandatedestination_not_allowed
op 0 pays GD6V2JMNWNQQSJ4ETHUS2TCH4DT5GYAB3OABS7T3NLLUYBXR7HZKUTDS, which is not in the allowlist
counterpartycounterparty_denied
GD6V2JMNWNQQSJ4ETHUS2TCH4DT5GYAB3OABS7T3NLLUYBXR7HZKUTDS 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
- c4d80b6307612a203f0cfe3f86a4216099ed5debbe3b51e97ae44a225e13d10f
- request
- 84c9f114d078642c39939a3b4cc0515c0e68f63c08ba9a416b3f7f964f09e8c3
- transaction
- e53f9d31e8baedd678c510cfb81525d54e79d2e4337816039ffd7484839a8062computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 44595
the chainentry 44595
- sealed to the entry before
- d50d9902e79c8dcc47de3b85a93e02190f9aaf004459a2710bf14301fb6fc283
- this leaf
- b1fd56149ce71c25166298cc4877b2de72d940915155c7f4dee20dcfc60fc9f3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- AQV0KUX4ybpBAVaYHhszCEr4xP1E6ciXxa6vAlGZlDOBmhvd3UavQcPeVxibuLT6kkV9+CFtO7yyyYOGUZhkDQ==