why1 reason
spend_windowspend_window_exceeded
this would take GDQC5W35ELIZR56VS6FHY6S3ZNGQSWYNX5KOSZWFRFWNGPBSDLPMVMZV to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- 8756be3fd2409269094d05f09964be1ce08b782c815d356ef2ba6b25f08796ac
- request
- 95cdf031c33211f54289fb89cec565c148b011aa211cdd269fcf201893f7b794
- transaction
- f91bc9041b519333567d0e232140a7bf4c0303783d21c31877eceb7b6bb7a895computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 6101
the chainentry 6101
- sealed to the entry before
- bed6f5033208e9b7f96deb89770d7e885a45e4ea28ae7d65288869c5c3affcc3
- this leaf
- a6290c7e7448a342619ad82a6ff26d14d1d27494d6c66919db107bffd298412a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- v6HscyAr1zVv+lfx0EXP4ERklXWvbI0iQBUjTwZH6nPaaRaANsHFljiEaWhrCW9bSu1IRMOTGd/7vVu3GNGnAA==