why1 reason
spend_windowspend_window_exceeded
this would take GBXHWJTWH3FQLF3WVI2SBF5LBJZWFJ7U7LYH6I3TBLS2OXCDLJ5JKFGT to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- e0b5ad874974c8023fa02ce22dfb5a708c6b115114a764008d27dc175a4035f8
- request
- 2dc114c643c4959d22c371b73c975885a3749e60936fb65ecf9bf26ccc94b106
- transaction
- bf19515e764ff1eb40fe5c3a78a81941d1992d9c93736e16cd485d6221ad99c0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 6435
the chainentry 6435
- sealed to the entry before
- 95a60130867fca2a141805446424afae76edc654f444f713f8a9f4885d7420a1
- this leaf
- afde6a3dcc3019acb418435242e16c2eed9c31cb7fb931456912f92b73502fbc
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- MX6fmrOWfny0FLEYZHDHty3PVOjvHbEMlHv7I36MeHbG+HXqMJsDfI7TEGfjPlp7kdI6ZTOnI424BFkBPpfXCw==