why2 reasons
mandatedestination_not_allowed
op 0 pays GD6DQPG3GQBIHZCSAUIG7SRHVJF43RXDHUZA3YNBOYDKARFVJVBTUULR, which is not in the allowlist
counterpartycounterparty_denied
GD6DQPG3GQBIHZCSAUIG7SRHVJF43RXDHUZA3YNBOYDKARFVJVBTUULR 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
- eeb5a4f7c0de23fc712c7b4a1386a5a021e8465a46ad638f5fcd7379e3dc4fa6
- request
- 0a904a59410d90ae705b9550c413bab51f1a145c8140baf88a62144e911bc815
- transaction
- 9c8c259fec52cd2279be966f04882c90cfb20da8c779d8b9c44c0cb66997825fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 9415
the chainentry 9415
- sealed to the entry before
- 7cf095ecaf4def96c45a0d2b18d96e753cc83c8f6300a92ea46a0a6ba9dc14ab
- this leaf
- 58e7ebbfb130bf1208682da56366929db7e1ce194ed36a42e45eb12e08c73d49
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ekidELEQz8kmwL7vZ55or6IQ0/1kZS9sNEGgrn6EnIFqsxO4S/+X4bMBMXsEXoJQ4TiJnAcmiadwYbjgV0EEDw==