why1 reason
spend_windowspend_window_exceeded
this would take GD3H2EOWKXYIWK6FVXY5WZGPVQNKIMBZVM4XIWPG2XUO6F4FRT2B4IX5 to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- a65b5cc89e18f1c723163f5bffbef687daed075055ce69dcca3a780285333ef5
- request
- 60e3e5d6e75a657dc2f175c57edbb235c3ebdb51585cd664f7d22ee76d0771bd
- transaction
- 4086b10b49faf05663ab5320a659178b272af7563812de074cd02ff49e135f0acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30732
the chainentry 30732
- sealed to the entry before
- 251235855b056b3b80ce6bf7f7aac0d86b2a5e45f680d835e3cd66f55ac39b78
- this leaf
- e2e69d8a678d96f3df605fa34a2cef585fd6490ca43f27ee7ee223794c2e79dd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- LhxH+fDm8+HZynZUaTHIGioWsMGn0Fp5tr5VWBzmpxePk+3rOuKwEoC/8uGueud0MTcLn2w+cKRS4kvlcZJgAQ==