why2 reasons
mandatedestination_not_allowed
op 0 pays GDPISQG3MI4UXMO2GXUA7E6UTUNHY3GTZN37BMI5R5DU6UJYKVSK7FKE, which is not in the allowlist
counterpartycounterparty_denied
GDPISQG3MI4UXMO2GXUA7E6UTUNHY3GTZN37BMI5R5DU6UJYKVSK7FKE 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
- 8bdeba74ba22665094e0250c93c2a5e0e571de63e29e23c0787639877f128ed6
- request
- ebe17717904a50a024d3a045e896f65ac7fe73edec4a531e5df1f640c73f9004
- transaction
- 97dff5c0b362d441e3b8b87786a495e3f630349c98553ce25b366f9e03369d50computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 55778
the chainentry 55778
- sealed to the entry before
- b4b7d487c05d06a8cf6b28508285cc4a7d0ae725da8cbec0c69b1f664e0718fb
- this leaf
- 2dc022c0b13e9b47fbda1a1be3cdda75da39e09e6d048c7ab650c4cd4d64cafc
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- cnmTQkBelB1IwssZMFvlWmWb+Lc+WHrzvG388/bCZ8YT/a1JPuFsy8TvSai2ItLdm5Aq1dMYQozbb60TOmG6BQ==