why2 reasons
mandatedestination_not_allowed
op 0 pays GB3AU6MEM5GQI6JJNCSELS3CDJ4W7N7QHXBYR4FSU7KAMSHWGKHHG6WK, which is not in the allowlist
counterpartycounterparty_denied
GB3AU6MEM5GQI6JJNCSELS3CDJ4W7N7QHXBYR4FSU7KAMSHWGKHHG6WK 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
- 9c1a62071e4a766b430f0531f5f24682542af264ed5472109e7fe1c23fb51542
- request
- 0e04baa3a9651b7e5b257cbe58cb7fc9357182b53683241b3c36c1b0880307f2
- transaction
- 18289487b9c0b9b53d4891dbba897e22a9521a074cd16ff79a7f66bd07eae34ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 16526
the chainentry 16526
- sealed to the entry before
- 334dd7928b1b5ef29a82fff7e4c27c9ed864966e03273250e8cf7f6bcbd294bd
- this leaf
- f4b40e3d6d20a9c2a9e3b99a9aed0115952418eae7cd09a7588ab18151d6b11b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- kwQOdygqNnn7xKYs7aOhhog5tvWQt4O3A4ARXc+jFICpXBbSV2VX0iiv/I77rLitU6q9JluDBdPVLoLmD46yAQ==