← previous blocknext block →recent activity
Analyzing
Block #86,978,002
19 transactions · 17 stateful · 2026-07-11 04:00:35 UTC
Parallelism
74/100
Blocked
53%
Avg conflicts / tx
1.05
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,978,002 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w17w28w310w013w114w315w417w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1941b441…5889
0x34b655…2a6f
10 touches
10 conflicts
0x2b95e778…d7d0
0x34b655…2a6f
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0xd1ec0dfd…ccc0
0xc8689a…ee79
6 touches
3 conflicts
0x17c3727d…cb0e
0x34b655…2a6f
6 touches
3 conflicts
0x1cbd009b…629b
0x34b655…2a6f
6 touches
3 conflicts
0x749e1684…ce38
0x34b655…2a6f
6 touches
3 conflicts
0xa3c36de0…3cf3
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x1941b4413e…0c5889
Audit this contract →
← previous block·next block →recent activity