why1 reason
spend_windowspend_window_exceeded
this would take GDRZ66RWH4RK5KAU26OTZ4ZZI7OAMPCQVDHTLZ7MPFGFQ3VPO4CC6INM to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- 14076f48b1ff4a22becf256ee2b9a251f43ec38417209002e9dcfab8803a6a2d
- request
- 2fe1e9d922594875991e661aa767fa9a56e49a90106ca26c62a465bdf0888e8c
- transaction
- 4ab605be0cce69fc2ac2b59d39b907931ea831f92cbf8332aec0b9db2d50cc6fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30149
the chainentry 30149
- sealed to the entry before
- 794935c5227afc2f1fb99779add169616010296e5c69f85edf1578931885036c
- this leaf
- 9c40552b380adb8e6ae6cacbb9b85958c230669f2875f088ac912595d45a1e10
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 7R4fA8EgRfqvfP6HIi/0DTSPCewUc35nML9ltt6Wra47Pq0NQSxjKu7dGofyXsy1fK+NnAdzNI9eWoI9nItsDA==