why1 reason
spend_windowspend_window_exceeded
this would take GCLUSVSSEQLPHNZQ32BB6IZRCIZBJVWOCUUE7PQUCR2UNXWTUHJGHXKH to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- f33422fa4a7f31457845501f07bf447a0549fcb8e2bf6ef2cf817f87ebfa5128
- request
- 4000270a04c67d13eca433ef9e6b249afd7bc28ae57e5ce938f2b70a1ab4cee2
- transaction
- 25f062ddcd690f75b7502d52d35e129b3b09b25bdb51abaa05c69c83237858a0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 7781
the chainentry 7781
- sealed to the entry before
- e27976085b350e5dd859d170c52fdf22d176677dbb1062716de444dbb3d05809
- this leaf
- 50f5a29769bde84b1be3664cc9c5f33f9dae0f316a84e10e841c9f5f2d62d100
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- gjVyPYNG5stDnDGFiczB6DmDlinNTVqCGlNBxtSJb69Eo6BR8wF0o9iOF9EpRvJAAP/TtGuxCRjdHG92nCzTBQ==