why2 reasons
mandatedestination_not_allowed
op 0 pays GDA5W63EN2EOPYMM4E7R3UO4DX4CL55X6SNLGVULSF3QQED43JM5FNAT, which is not in the allowlist
counterpartycounterparty_denied
GDA5W63EN2EOPYMM4E7R3UO4DX4CL55X6SNLGVULSF3QQED43JM5FNAT 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
- 78555e17b38eefebcfd2dc553a978de938caf354120cbae5e1acb641f350bb65
- request
- f6f2a5a56e2b3656ed833e997fd32b3b465785c982900b7c14173cf20bc1dd3e
- transaction
- c5b7a9c048e3b98bfa3c0e7d6319faf2defe4cdff7eb324f50e89ac6e6549c83computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 49277
the chainentry 49277
- sealed to the entry before
- acddfd4dddf5db730480f6bb4ec401bad06cfc688dc79319fb67b8c8c571f873
- this leaf
- 92080958c0a53bb6b7429746319662ea3e9ef55688c8ac6a40b865cd75894435
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ct1fMLMw+o9uyOXJOYnigvZsXDSt0L3asLcEpPPnSc0dhWxKkNwIJEjDZD/gz94s2YT3B0zUURY7l9JzpiK2Bg==