why1 reason
spend_windowspend_window_exceeded
this would take GD7HPP7CKK3KCWK5SNNN4RP3E5CR76BNXCVPMBESU5VKIWRHXC4VIU5B to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- ef505fc3d0ff9ca05221cc9cc9d6f0d416c4c8208878b543bfabe6d73761a625
- request
- 604191474e189dcc0ce3059a79ac16d3478cebc7170cf5ae4f182c8811078e51
- transaction
- ebccf3220ab309aeb528f4c8166e0f1364d1720015e4ff32452e7c7260754e97computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 38601
the chainentry 38601
- sealed to the entry before
- 7c8c3d9f7c1913cef077a81643dadceaeb899cc408495cff2a80c7a34914b49b
- this leaf
- 01e659005be8eafe7d2da23600214fafc9c524fa9b3ce9c76b97ffac1e0cd4ab
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- sUdvAmYz+uzljo5ZwINW7z3mqE/6Fa/cHdSUt7Xv7Zxu1k5LLo4iiXL4mD7jNkqYlej6rMUrKkOwHeVVNTbfCg==