why1 reason
spend_windowspend_window_exceeded
this would take GCKG7M5E3C2OV7U6KMEYRMMUCK5P773QKVQIQ2QHOL75UPGPFL5UB4WZ to 108 over the last 60000ms, above the 90 window cap, with 78 already spent
what it was decided fromfingerprints
- rule compiled from it
- f261e2692769abf5026b356e83510f8f69c60199494377b009c3766747795993
- request
- d21cd26b5c79fa1d51f79028bfb549a88799114df60f13b7297e75b0b901341e
- transaction
- e81dc0fca65fd3015f8b6f7e1df7f90100c96ac708443fd1e2bfeac41551151acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 65790
the chainentry 65790
- sealed to the entry before
- d4085825f3f67d391eb1bdade38c1f9ebf60a72cce2a67e8c00aefb9023c149e
- this leaf
- ea43ec2b12a60d65bda1830a5e44254edb68d5c86b71bdfd2f7eb3ac848ca7c3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- HrDX2zbycWznos311rQ8DiaYr0CcKsJnt0GRlkrAZh3+NrzH2xAz5f6XSQaLPaf4KCGQs+0Zt0Za15E6Q04bCw==