why2 reasons
mandatedestination_not_allowed
op 0 pays GDTHHEYW33GKB723WYGRRV56S4EXD4CEAGBWL6XP5D5OMFSAA2OASDCP, which is not in the allowlist
counterpartycounterparty_denied
GDTHHEYW33GKB723WYGRRV56S4EXD4CEAGBWL6XP5D5OMFSAA2OASDCP 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
- 0c096f28f8d3375be59cc0c87faf527506d93eeb31e8620f9fd9e58db4abdf6d
- request
- bc5df4d3cdb260eac6817931ca99674bd2a1bc83e61eef1b483ded171dc1a865
- transaction
- 454e4a242ee6068bdb73f155fc821e579e49ae4276172bbe12cfab3f16f52ab8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 39169
the chainentry 39169
- sealed to the entry before
- 42ecca2783d284fca17e2707cf791e2fe62eb21b0824bfd6ee66d1245b54c3ac
- this leaf
- 680272b4c847d80cebeaa98e62cfcec46b40576da51628233b21ad8a3fe24c81
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- NIJjwvF5+WumClbnNpp2vG0pe2lUp8tadsAQfjeUIBotRm2vJ8+D1Ge7rrLjFozcmlSv8AlDExQLxj45vmfeDg==