← previous blocknext block →recent activity
Analyzing
Block #88,357,408
16 transactions · 14 stateful · 2026-07-17 13:47:28 UTC
Parallelism
56/100
Blocked
43%
Avg conflicts / tx
0.63
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #88,357,408 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w18w212w313w414w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5ed3d97e…1bc6
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xb733b9da…9c31
0x34b655…2a6f
6 touches
3 conflicts
0xc5ff7803…2f13
0x34b655…2a6f
6 touches
3 conflicts
0x75755da1…f498
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xd064a456…b881
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 0x5ed3d97e9e…d51bc6
Audit this contract →
← previous block·next block →recent activity