why2 reasons
mandatedestination_not_allowed
op 0 pays GDQRQRX72VEGZOZMM5AH4SCSRJ3BUEPIEUIGBRE53KY6DM7WJROM7DBD, which is not in the allowlist
counterpartycounterparty_denied
GDQRQRX72VEGZOZMM5AH4SCSRJ3BUEPIEUIGBRE53KY6DM7WJROM7DBD 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
- d65d9c560fb14aefe237b198c2c02ee64d3a94067b104be381e3e1cc68db0e1a
- request
- aa0f5d342acfd74df4f43ab11eb843b3d4ac68671b1f2f25429edc7fb36934be
- transaction
- 24b283d786f96b595def3ce1d6ff6ca44a5d6af21f98a801474d667621a155ebcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1226
the chainentry 1226
- sealed to the entry before
- 40ff2795b0f88b5648a1a06a62713713fa6cea6ac479e491fec0c5ad6b52f41c
- this leaf
- 8ddbe4fa90f029a15a15e891aab03c7eef32fdab79371eb07f338441670d4a2b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ZBg7OFEY2gPThwGRQ+otrchweu2FqLN5EJ/eN3lKQJQsC+E+yqtKmr8aE1bMbrLfebTXm8pHQma02XGzQU9sAg==