why1 reason
spend_windowspend_window_exceeded
this would take GDKEMCHRNVDGK7JKTBI2SBTLM6UDCI43W5S7FQPKYVRKAUEL3DDFCFGB to 108 over the last 60000ms, above the 90 window cap, with 78 already spent
what it was decided fromfingerprints
- rule compiled from it
- a7627dab75a15afcc300ad265c69f6489d22a1ed1d968bc2a73b4e089ccd7272
- request
- 39d4bdb80560db3dfbea2374b21c64c3145eeb2dec92b3d792b1b5d010f10e32
- transaction
- b3e3d1cf9fe2283822c5423f92d5ede8c64591ce55d19e210a80deaf8ee33941computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 66635
the chainentry 66635
- sealed to the entry before
- 3a0c7d7f8b61118364b68ca4efcc1f4908facdbfd6ec8ba67240933d9b727052
- this leaf
- 36a35d4f0888806e1cfa856efb392d740607a1f43fe0ccdd2cb630405c875cd9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- bb8yu4U1SeRzKBPh7k2xmJerZWVvCroIXBGp7xheVzzd0dsqMxQ8yMz1eGJ1CnWmOaZ7hKoJSeme8odg3i0uDw==