← previous blocknext block →recent activity
Analyzing
Block #86,675,614
25 transactions · 19 stateful · 2026-07-09 18:20:03 UTC
Parallelism
84/100
Blocked
37%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,675,614 · 25 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w211w113w214w321w022w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x56b5f5c0…a3ad
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x2bfb71b5…3a04
0x34b655…2a6f
4 touches
1 conflict
0x2bfb71b5…3a05
0x34b655…2a6f
4 touches
1 conflict
0x5cedf778…a79c
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4a2
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4a4
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot 0x56b5f5c03e…07a3ad
Audit this contract →
← previous block·next block →recent activity