← previous blocknext block →recent activity
Analyzing
Block #87,623,843
13 transactions · 9 stateful · 2026-07-14 03:59:54 UTC
Parallelism
77/100
Blocked
22%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,623,843 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w08w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xd7d3e7dd…2bf3
0x34b655…2a6f
6 touches
3 conflicts
0x5bb46f6c…7693
0x34b655…2a6f
6 touches
3 conflicts
0x99c46e97…c1b2
0x34b655…2a6f
6 touches
3 conflicts
0x3ca9a061…1f41
0x34b655…2a6f
4 touches
1 conflict
0x5ea6f0c6…4801
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x875c3459…2878
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