why2 reasons
spend_windowspend_window_exceeded
this would take GD6XRAZHSVZR2Q6LNOSP7FWZ2EP45E5SXNSEQPO5N7TLDFU3JH44JZV2 to 70 over the last 60000ms, above the 12 window cap, with 0 already spent
mandateamount_exceeds_cap
op 0 pays 70.0000000, cap is 40
what it was decided fromfingerprints
- rule compiled from it
- de3badd1e1d73fec244e1029cd2ed48e6e7cee41862d78ad72d610f5d655b676
- request
- 54fb9999892a702cf89fac22f47e9561f663b1d0a5fbe00f820fa07ed0bc5b51
- transaction
- a5eda51b4e004855aa4b1c1de024709df477eb7eb3eb42c789e7ce08050505e4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 19006
the chainentry 19006
- sealed to the entry before
- 5707070fd270c3977f077b6a9558a5ca4d63a9668a8a763fd7cb04252eb79462
- this leaf
- d675445d6fff4cdee3d8f9cef6a1f8bf21badb1e69e0e2758eb0a0214bf25c2d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- DbHSkMbx0eowXFRuGvsOIkKRJQ6O61B8tBbmabEAUMQu8NtojR6DFAKnNi36AhPdLyk5IvAKhJzhXh5/pOygDw==