← previous blocknext block →recent activity
Analyzing
Block #87,753,368
16 transactions · 16 stateful · 2026-07-14 18:26:18 UTC
Parallelism
63/100
Blocked
31%
Avg conflicts / tx
0.94
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,753,368 · 16 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
7w08w19w210w311w412w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
12 touches
15 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0xcc616f7f…6178
0x34b655…2a6f
10 touches
10 conflicts
0xf481b267…dc7d
0x34b655…2a6f
6 touches
3 conflicts
0x33d170e2…2c62
0x34b655…2a6f
4 touches
1 conflict
0x3631dfee…0125
0x34b655…2a6f
4 touches
1 conflict
0x3edaabd7…b9e8
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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
15 conflicts on slot 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity