why1 reason
spend_windowspend_window_exceeded
this would take GDQFE6DNKTJUKV3VCZ6EGH723IC5ZP4QCNWBF3FXLB32VYGODAFWOMHN to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- bea9bfe72a37d5a3f928429b51e70a8d573aacea482ec7f6b925d11ee45bb614
- request
- 548724a13b86562f2d16aa6cde9673286af784cb3b6f63ae262ae4d474687940
- transaction
- 62d1e1be6eb0792b830cc4057f6056819a2f343675de846cb44b6e2daf4165cdcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 6449
the chainentry 6449
- sealed to the entry before
- 9a498fd17b2eefdd5c32316d9f4f0aded31f50575b627988d81e16f23171a4ed
- this leaf
- 8f5317a1ca8f5dee0333dec240b0072b73e7df6b47c65ce4b50d47c5c351f921
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- t3zGYOzyVpMbHVOE3oWOA/gcD/xCZ7mJE7FZ0z8MEEuTERc3Rpzizi5kRcppo9uAHIwkKKwPGjirChp7f63mCA==