why1 reason
spend_windowspend_window_exceeded
this would take GCIEN2U45ZQ43CJXHS5I7GDQ6NKXOXFHDJDDYD4YI5LZKYGUOY7G7OLP to 108 over the last 60000ms, above the 90 window cap, with 78 already spent
what it was decided fromfingerprints
- rule compiled from it
- 619220a7ec42ab781fc90cdd0377d14994e47547398c2ef4f63cd62f29586994
- request
- fde9b3220f6754aa22ec311aca8e1cac5762976e2c7fcdcd0d99622335768a64
- transaction
- 9b8c4ac649ac36f11b88837f6cdb19f247ce16f6c8e764f28adedae0585b7aaecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 40403
the chainentry 40403
- sealed to the entry before
- 120d572d1bed0cd592e312d78c8e6fd2f5587c0b3ae44e116867c1dce18e3309
- this leaf
- 3c4875e7c67f85062b0e0e05a697c248dd2debeb1b8cfd608524e8c56108265f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Ihm3qJRhrAqGd/mbLgtYFmjuxj+NRGZ0MkbAwz+OYNqrGuS6WLKNbsdfZyiwa4CEj815++zMMYfTjeIMJ9gTAw==