why1 reason
spend_windowspend_window_exceeded
this would take GBHBR3IFHGWRCXW7FT6VEFCL3SSKCVFF3XG4KAXXGUKKU2TZYH2VCXEH to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- 64034eca262f222cb2ad02892aa523a0d7e133a16885f3f9fc9657350333836a
- request
- 13a4289c262f34db09c53ce30e3af13ce1aaaefb210ea04d5483ec03c535edf7
- transaction
- 605bdffc5fea565a7b75c28533021edd51b9b9d11f6018e0c80c02b98883efabcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70122
the chainentry 70122
- sealed to the entry before
- 5c43b5f0f44b7166c39cd049fcd508f51159c49414a5a8225ba608c408453220
- this leaf
- d2800965f58613edd87fefd2cc7e2bbc86a6fac4382d958e53944aeb293671e2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- mcQXwkrZGlsQxKbGkzWT9xWmCTiwKL0VrvQHg7DBkK78378wbzkZTEr5lMLR5ehtXJ+1wRI67zkNP3K1Q+jhAg==