why1 reason
spend_windowspend_window_exceeded
this would take GB7VT6SPY32IHZXUDEJH3GECRCTRVI7FGSMSPQTCXBYGX2JX6U3QUVE4 to 108 over the last 60000ms, above the 90 window cap, with 78 already spent
what it was decided fromfingerprints
- rule compiled from it
- bc1b5f3eb4d90e0b4de76ee5f3c42339f6ec5fdf699aac9b518194381f333d10
- request
- 5be00b81d47f85004eba2bc8659a2581c1d5e4fe34b39f5ee4eb6b31073d686c
- transaction
- 56fd892cb374299bac418c0861104d4e024c0cf5fbb848205c74844a8be92097computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 6620
the chainentry 6620
- sealed to the entry before
- cb94f6c77effc158514280f216bc9e6f02e6278dd0dfb84ad95ee75334d16c30
- this leaf
- e825058bffe3fab6e89d78324950e332a9810b81c48acca3dd715d09ca7abee2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2W0PKzFL53nG0dWM3ux3L+ASySRq5b/XNgHQo7GbU3R7C1DngzJZXPJY4Qtv5u08lsiZUK/LKeoAwOpzTi6FBg==