why2 reasons
spend_windowspend_window_exceeded
this would take GBRQDPPQVB5X7XRGX6OCS6BVMHHXV5ZFH575CU6F7HDO4NMMORBX6MYP 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
- 6f1dae806850f5a408aaa38cc151a14b81a87177f99665914fbc18386ace3f60
- request
- f950c3a6e473c37c0c3799ff400d56ac880bff2bdfcc34eb249ecf5c7dd6e673
- transaction
- 480daae16b50e56f4d8bab1c793c0e8e355b657c6f8980874e45ad762d7a2106computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 16544
the chainentry 16544
- sealed to the entry before
- f1468ffda1d836fe073cf14dcab35120f9bf24123889cbae537db74e3ff36b29
- this leaf
- 9353696819d995022b2b56e0ce026791ce1993177650b4a1cc37f662883eb82f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- f+4X86qBxWkZLQFcVfTsqDlGmywTu33aA49Ax3LKweTa00fVabkx5GDlo6oTyz+R1sgRCjBQ05nLSrrsqzg5BQ==