why2 reasons
mandatedestination_not_allowed
op 0 pays GDSDBSHI3Z4LJUQWH5HOAXGNNMXSK7P25I5J7BEEXLYMPEW2QGCMDZ45, which is not in the allowlist
counterpartycounterparty_denied
GDSDBSHI3Z4LJUQWH5HOAXGNNMXSK7P25I5J7BEEXLYMPEW2QGCMDZ45 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
- 2ade5f6422235c64477429f075fefa44b58d1ae9b67892b922be7d7686bdf032
- request
- a2312ced884cbcd66a30f07e84e9abec467b5dc77c321788f9ba3bd9b886ef57
- transaction
- 4688b7a390adf169edf90e35360fe4918667aec0da193611b338d1fb37118958computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 42286
the chainentry 42286
- sealed to the entry before
- 1069a66427d35bc64a121c1a28ad31d98bb937cb1b2807846c076cd3cf833618
- this leaf
- 64f6e2b638f56f7e90bff6466c28256ed7f5d7f2402ae3c95242db381d604415
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- mfJAQWeS2PYKPgHi+1aYOKiRY/JznNi2QX90eYtNmWqNp0S6PNXhKwHTKNrYtJu7RVG8beVGb+Mewh28N++DBw==