← previous blocknext block →recent activity
Analyzing
Block #88,079,718
16 transactions · 14 stateful · 2026-07-16 06:49:08 UTC
Parallelism
81/100
Blocked
43%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #88,079,718 · 16 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
1w02w16w07w18w19w110w213w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x62b13313…bbe8
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xd5c56995…6d21
0x34b655…2a6f
6 touches
3 conflicts
0xd5c56995…6d22
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x301e1c77…9e30
0x34b655…2a6f
6 touches
3 conflicts
0x8391fb68…4c83
0x34b655…2a6f
4 touches
1 conflict
0x91259317…9e70
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
3 conflicts on slot 0x62b133137c…31bbe8
Audit this contract →
← previous block·next block →recent activity