why2 reasons
mandatedestination_not_allowed
op 0 pays GDNESBEEAX4MYAWOJ2XWZQU2SBA5GVQ4ZDTRJAB42TBF37TYCPOXHBFM, which is not in the allowlist
counterpartycounterparty_denied
GDNESBEEAX4MYAWOJ2XWZQU2SBA5GVQ4ZDTRJAB42TBF37TYCPOXHBFM 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
- ffbee2d7eede664a1fcb34532320fee37c2cb94b20dddd2f687c961bc29d92cf
- request
- 989ea9b0f3929ea86c4978b9f176dca9a330d93dcfc56fd7b599eaa69f3aa373
- transaction
- 22361f840d1bfc3bdec7c9ff4e91ebea35bb38c692940320156000c27755f1d7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 297
the chainentry 297
- sealed to the entry before
- b272744a361d8563815b58853a88ca1671701e2e9b81189127f9fd608e0004be
- this leaf
- 363bd275ddf164a3c3c74fe6d08cde1936524701da0cb4e6b7274402091aaef0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 64K1zgKiw/IXARCP5Whn0qvOYsxh4wE/eoaMvG2V3ae/4n9iAgd17muZb78YWXG83hJ7XhkLBUqcQrmsyijDCA==