← previous blocknext block →recent activity
Analyzing
Block #86,788,328
16 transactions · 14 stateful · 2026-07-10 06:52:44 UTC
Parallelism
69/100
Blocked
29%
Avg conflicts / tx
0.44
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,788,328 · 16 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
5w06w17w28w310w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x013c31f5…a718
0x34b655…2a6f
4 touches
1 conflict
0x021df0f6…5d6f
0x34b655…2a6f
4 touches
1 conflict
0xe6a34ca2…4075
0x34b655…2a6f
4 touches
1 conflict
0x013c31f5…a717
0x34b655…2a6f
4 touches
1 conflict
0xc7fed9f9…f3a0
0x34b655…2a6f
4 touches
1 conflict
0xc807ba51…8b7b
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
6 conflicts on slot 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity