← previous blocknext block →recent activity
Analyzing
Block #88,184,717
12 transactions · 11 stateful · 2026-07-16 18:32:11 UTC
Parallelism
75/100
Blocked
36%
Avg conflicts / tx
0.58
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #88,184,717 · 12 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
3w04w05w17w08w19w211w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xffc2f21e…b393
0x34b655…2a6f
6 touches
3 conflicts
0x42041fec…bd86
0x754704…b603
6 touches
3 conflicts
0xd7668c61…55f8
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x2697123c…8526
0x34b655…2a6f
2 touches
0 conflicts
0x2f461725…5ab2
0x34b655…2a6f
2 touches
0 conflicts
0x2fade833…5de4
0x34b655…2a6f
2 touches
0 conflicts
0x3c0c2f32…c3df
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
3 conflicts on slot 0xffc2f21efe…ecb393
Audit this contract →
← previous block·next block →recent activity