why2 reasons
spend_windowspend_window_exceeded
this would take GD6VPQW6AZ5WSV4X62SN7YHXM3G7O66EYKHOXPCNQ6JQNS4DWN6RBSXI 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
- 682dfe81d88cca46936c58de0e84bdea2bd1e14e2429cda96b6587169c4404e4
- request
- e36c5ffbf15dc612e1586e3ca4bb613a9568bfb5906d50f5daea4f80a8fcbba1
- transaction
- 7d07f0c2df4ed2a7c8f19a950f5aaa152b264322450bab259a5e843c4cff5941computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30691
the chainentry 30691
- sealed to the entry before
- 6b252d46d7ecc5eaff918db8ad442d1e9bf9637ae120d12e213e3f7878080efc
- this leaf
- 5d76f6efac5d2a2a957aba12f30fb2724ad8b8a1fa2ebff451deede139a2d364
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- LQ/gShdIRruUFgIolulQy2UDLr/zdKqL+v1+Ub0FnOSHxNNJp/vKtn0uTnzROfzFLrZKQfxD/Ck7KEsuUZXfAg==