why1 reason
spend_windowspend_window_exceeded
this would take GBQRIAEDNV5VMFVGK63A5PLZDA36KJ7D24EWWQ5NFXTHP5E7TIBZDJIW to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- 4cdbc24f50056b692c470f21af6ee604fdece041a5ef4303df9b2db854ece507
- request
- d45175dec04dfc90d66c97e8363be70d2c83674098c4b62b663ab21507988fa7
- transaction
- 530c3357af954bc603289e1c46f3bf3f0c21f1fb48cd289ce273b86bb49d11b0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 13133
the chainentry 13133
- sealed to the entry before
- 8151261108ad963ac8e7c524e278dd30a26f922c0a98c4533c4bca370c47fbbc
- this leaf
- b313ca23389f63fccf65b960a40c553b4605f4178b168712ff3cd8fb6291ea9f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ugRjjOaQYeV51puxL36o+6nngMMymcMf1rtmQ9Io9NrChfG0AC1vpdJNpOUW7/aScL8RMdT1R7R0WBoxQonCBA==