← previous blocknext block →recent activity
Analyzing
Block #86,803,712
41 transactions · 36 stateful · 2026-07-10 08:35:29 UTC
Parallelism
59/100
Blocked
58%
Avg conflicts / tx
2.1
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #86,803,712 · 41 txs across 17 waves · depth 17
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w29w312w013w114w215w316w417w518w619w720w822w326w927w1028w1130w434w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
18 touches
36 conflicts
0x8d888c90…5479
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0x4f7ade32…4641
0x34b655…2a6f
8 touches
6 conflicts
0x0f4cddfd…3085
0x34b655…2a6f
8 touches
6 conflicts
0xab3ba25f…ec78
0x34b655…2a6f
8 touches
6 conflicts
0xc7ac2c0f…f591
0x34b655…2a6f
8 touches
6 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
36 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity