← previous blocknext block →recent activity
Analyzing
Block #87,316,855
14 transactions · 14 stateful · 2026-07-12 17:46:06 UTC
Parallelism
71/100
Blocked
36%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,316,855 · 14 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
3w04w15w26w07w18w09w110w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x64aaadbf…f9f3
0x34b655…2a6f
6 touches
3 conflicts
0x4250b098…c70c
0x0a2fbf…29b1
4 touches
1 conflict
0x84e048fa…24f7
0x0a2fbf…29b1
4 touches
1 conflict
0x84e048fa…24f8
0x0a2fbf…29b1
4 touches
1 conflict
0x4ab0fef9…caef
0x34b655…2a6f
4 touches
1 conflict
0x59a5e379…ad8e
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity