← previous blocknext block →recent activity
Analyzing
Block #88,341,926
15 transactions · 15 stateful · 2026-07-17 12:03:28 UTC
Parallelism
67/100
Blocked
47%
Avg conflicts / tx
0.93
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #88,341,926 · 15 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w16w17w29w110w311w412w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6ff15a3a…da05
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x557aa673…6559
0x851145…3f07
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
6 touches
3 conflicts
0x799aea28…88dc
0x851145…3f07
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0xc7f6eab9…9e9f
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
6 conflicts on slot 0x6ff15a3aa7…1eda05
Audit this contract →
← previous block·next block →recent activity