← previous blocknext block →recent activity
Analyzing
Block #87,667,389
23 transactions · 20 stateful · 2026-07-14 08:50:55 UTC
Parallelism
74/100
Blocked
45%
Avg conflicts / tx
0.83
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,667,389 · 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
2w03w15w07w110w211w312w415w116w517w018w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0xd97c2fdb…27d5
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x4c188934…158e
0x34b655…2a6f
6 touches
3 conflicts
0x4f4a7ac3…021c
0x34b655…2a6f
6 touches
3 conflicts
0xee0cc1b7…de22
0x34b655…2a6f
6 touches
3 conflicts
0x1f40ac22…24cb
0x34b655…2a6f
6 touches
3 conflicts
0xaedc3dd6…3c3b
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity