why1 reason
spend_windowspend_window_exceeded
this would take GBBSDW3G4T63JC4QBX7BFGL7L7KEJLZNNZBEUT3R5OOO5ZZEWRFRLCP4 to 108 over the last 60000ms, above the 90 window cap, with 78 already spent
what it was decided fromfingerprints
- rule compiled from it
- c6aa78148995d4440745cfc63ac33c52a7a5ee287a9892249ded9999df38e81a
- request
- a7d41b5fb7cdfd4d9407f5b4735b27477259851ae25c46a8dd86f01c1e781225
- transaction
- ca4a100ca8fa25bc882652f295b5e8732aa74bec1926cfcb602aa2e51fba79f1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 69053
the chainentry 69053
- sealed to the entry before
- a48c5d1f867b5e4704453eaee4ffca7b27c448cab43f615e90659714c493fc5b
- this leaf
- a9d58c0eb8331405cef956dcd00a762fd6d1b9aebf5b7e44da657636ddf95ec8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- eAf6lXJr58Fbhrp3jFSWeSeb66HZsBkSyqX9MWCwf3D6/+VTXTYDwSb3aYsWU+9rOsg4ANp4dxVT0JqbZehLAw==