why2 reasons
mandatedestination_not_allowed
op 0 pays GAOGKEH4NHASSWGN452WUUSE5CLOHUPRFEMAZPFQOWQR7DMQHQI5Y6RB, which is not in the allowlist
counterpartycounterparty_denied
GAOGKEH4NHASSWGN452WUUSE5CLOHUPRFEMAZPFQOWQR7DMQHQI5Y6RB 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
- 7e71cb387a2418d0737b026d6ad7b1f8c3dd35e1d15002172b2b7a53c85b35ae
- request
- 2cb164a74d210c917ef3e4808bd757ec75b19a29512a4d88f1fd965c763faf79
- transaction
- e40d94cc75262f8a2d049222c64f7807d5c88cec93879da5a057f1fc90692d11computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 76106
the chainentry 76106
- sealed to the entry before
- 108280aaec20a80aecd7f3c653e8fc170da3a01be502118a2582e82ca0a0fbcc
- this leaf
- ecb4062c064d3dd05ab2bed26a54e2bc1bec297efaa3dd1133410823d5457b3d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ltus/s5+PgxCSIox9A6ehoVKM+5RuWeSdi1GpW4zva+EmMOXPRABmYvvP9ucRLW4rK87j9KmbsnP4UxWaDyzBg==