← previous blocknext block →recent activity
Analyzing
Block #88,343,111
11 transactions · 10 stateful · 2026-07-17 12:11:23 UTC
Parallelism
82/100
Blocked
30%
Avg conflicts / tx
0.27
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #88,343,111 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w07w18w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0505bae8…b4fb
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd379a368…fea4
0x34b655…2a6f
4 touches
1 conflict
0x18e900fa…07f4
0x34b655…2a6f
2 touches
0 conflicts
0x1e088f8c…99c7
0x34b655…2a6f
2 touches
0 conflicts
0x217b42a3…ac58
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0x0505bae898…14b4fb
Audit this contract →
← previous block·next block →recent activity