why2 reasons
mandatedestination_not_allowed
op 0 pays GDBC2H7K7GTOTHGQ5WGGPT4D6JZQNHRIQFWNGIFYHK2A6QAFINQOR5HL, which is not in the allowlist
counterpartycounterparty_denied
GDBC2H7K7GTOTHGQ5WGGPT4D6JZQNHRIQFWNGIFYHK2A6QAFINQOR5HL 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
- 97b817f878b4a17ecec7745833cc2a8f4bf7e6ca751e3af02e71cefff4dea780
- request
- f5165107468104d257ebde39d67007099b13e3ba8d36df124e272a3de46d1180
- transaction
- e828cffddb4d3e0d621aebb602b0e909e6e8ea9fa911afb0c76ade9559f5e6dfcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 58271
the chainentry 58271
- sealed to the entry before
- 14f29f9aad292f3128be54b576904faa5d3bcb90bd7907863eb134da144d7f2b
- this leaf
- 80e61065b0cb93db10178cfdcf04866bcce90e65fe6e99ec5d4745882bf0c6b6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- nn3E8FazhMZeGG8da/wMJ3ZNTQU3DFe/Xoum/UOYM5V9ZyMTX5e3Pq126iMDpxS4DMT2hS3q04ar1VIUqwGpAA==