why1 reason
spend_windowspend_window_exceeded
this would take GB7KUXDIO7KFEDAAWBUCOAE5XZMVTEN7QUFGK6FAHKGNKL3AK5LMJIRT to 108 over the last 60000ms, above the 90 window cap, with 78 already spent
what it was decided fromfingerprints
- rule compiled from it
- 443c34c8d776f8d02230ab8b08747380a9a9b3b2dccd9e56a80c61b1eba7dd75
- request
- 211fb1f6267475fdbe9898be85e068e545f90f17223661b06b9644afcde86c50
- transaction
- 4227447aa73e14258d4d86b60040cad8bd7ca47193c9514db1d1c8736928fbf3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 3340
the chainentry 3340
- sealed to the entry before
- 30704e068c936419c97b5be63bf13a9f45261270125e81a9acf1a9a1fea7c683
- this leaf
- beb7816c64e7196cadb07a4baddd6ec9b1de42700d85b1f21e13652de0552314
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 38sN0FVZ0tTL2qNSyGQaej460a6kmjJSrYsA6yuwZyna9+mECZ0XicCmnC8PDVt5mbpqKSgwetsSzq/+THiiDw==