why1 reason
spend_windowspend_window_exceeded
this would take GC35WJUCXAWRFJFOD4E447J7WSHGCKRM4MJP6UFBCZ6PSTUAMTT5DNAX to 108 over the last 60000ms, above the 90 window cap, with 78 already spent
what it was decided fromfingerprints
- rule compiled from it
- 0a375e1fbbf0f6793bfb44d4b8cc4979c7c4d8c1825f6309e9495912bde072c9
- request
- 50ede348a448b2597237116d53b2047d2f07f6c6e3f14ef31121615839aafa56
- transaction
- 76a0fbfb466e434980a941eb08544856f6c5e7520118041d5236654ca41c3fa3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 41446
the chainentry 41446
- sealed to the entry before
- 0d7b1f3504aadef0617a14cbd5029920d9a9690a4474a567873ca9815985cc99
- this leaf
- 2056a0c2085c22d3e9fa0893b53209c6833b1ac0bf84a73a39d7cf3004b0e3b4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- xvCnusQsBECyXjVdMJH0KgTeuEDqJ1S/FGm0sK6N2+OUVtbVEhZicx1bv0iCyTyGu0whzdT4qNkMSkhAMP1HBg==