← previous blocknext block →recent activity
Analyzing
Block #87,616,628
23 transactions · 17 stateful · 2026-07-14 03:11:41 UTC
Parallelism
74/100
Blocked
35%
Avg conflicts / tx
0.7
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,616,628 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w18w09w110w213w314w421w022w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x207b4a17…4084
0x34b655…2a6f
8 touches
6 conflicts
0x46d5a052…ff2e
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x7840c762…8060
0x34b655…2a6f
6 touches
3 conflicts
0x8cf506bd…f8d6
0x34b655…2a6f
4 touches
1 conflict
0xa0af25f7…9129
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
10 conflicts on slot 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity