why1 reason
spend_windowspend_window_exceeded
this would take GDYTN5P7H7K6Q36HIWPF6XWKWUKJPQYRD33X46E4LNP4KMIR7QZUIFK4 to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- a15c6658a3ae8043398f529ca17e71f8c05637f824d80d37cf8b7af855c9bd54
- request
- d423d50517639f357ecad3c285e6724782c5692f3cea00acea01d5fefd09cbc4
- transaction
- 4e83a7bfdab66c99072bfb59854f9db660f127408a3ac4936a43c774f60942a9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70687
the chainentry 70687
- sealed to the entry before
- d48c0a4234a2d457839018062ecda501af7e956ef601f546313d44485e654488
- this leaf
- 7d8736ce3a8d49dc33d0d8e780e2f5c4d8c6e5ada31bf68b7d7e0fcac364adde
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Sf9/K10EtpB/LNhy9VAOGD4SLt4BvelH6GmywTNTIscLNoLA4jYQaLJw6IPD8Jl+79ciUncqCImAMsSJ9yo7AA==