why1 reason
spend_windowspend_window_exceeded
this would take GDSRDEVDCVYSQ7CB5NAQKCGYCYR5D5QUNAOULRXAKR4ERZ6QNOWG5L6S to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- 3450d7f7a75d6edd0c5de1172e0fb4f14afe979e9096066a74a2a38a00df4b47
- request
- e74fdbba03b64f08035f4831c34c512874b92546dda1a8c6b562208ce9bfae26
- transaction
- 5a4e041be87c76d4bc52c1b2fa6e0fcede1cf9147b2577bd7f3b97c6f814f6eacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 42966
the chainentry 42966
- sealed to the entry before
- 5bd44b89e95c9d28ce3f602770ace60c610e2dcf03cee366c8e07dd362e1af21
- this leaf
- 3a757fb5ea5e60300d2b09569431c5383a58861709cae143bee7e18305a3c2f3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 5M/7W48BYEZ2jHOTnKYi2uMZMFlr/sDehWY73TxE8q0cA0bXSIfeb4fKmPLoMMYpN6ojd76oFDaWxDHMWOIzDA==