why2 reasons
mandatedestination_not_allowed
op 0 pays GB5HFVD4XCZ6IKP23U7D5JJOMUGV4ZJLQQYHMTYVCKXV4HB6JTH2VGQN, which is not in the allowlist
counterpartycounterparty_denied
GB5HFVD4XCZ6IKP23U7D5JJOMUGV4ZJLQQYHMTYVCKXV4HB6JTH2VGQN 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
- 153ec5cb476b1a4825d3be13c8fcae976f5b9c23adf8313bb88e8db56d86412c
- request
- e2e83994bf74f1a0bc058be949f6427514663c77cd9a85ff6314fae5fed13efe
- transaction
- 504cadeffdf68d316229f7cac7ba3ed24bbb955f1b9ea7b1e2cf7ddb132a8cdccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 75440
the chainentry 75440
- sealed to the entry before
- a252f484d704fcdca4cc5aaf0f256ea2870097134f57c72124a5b0d5db1ed1ef
- this leaf
- a46689540c5b4e0ddf2ad71bcc88cb87ce16fe93d18869c03f7eb1cb6b7fff36
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- s7aM63yd+FAVRtMgcNgYOECZS9ecJfzSrDLkS5ZPtXPOHCKbppsH0LMEAo9UmKGiyfDBLYlp3a2z3dszRTcwDA==