← previous blocknext block →recent activity
Analyzing
Block #88,350,899
12 transactions · 11 stateful · 2026-07-17 13:03:31 UTC
Parallelism
75/100
Blocked
36%
Avg conflicts / tx
0.67
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #88,350,899 · 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
2w05w16w07w18w29w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x64800813…db9f
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xae67b206…8b00
0x34b655…2a6f
6 touches
3 conflicts
0xb9834665…e363
0x34b655…2a6f
6 touches
3 conflicts
0x50e84e6c…287f
0x34b655…2a6f
4 touches
1 conflict
0x61757a59…d89f
0x34b655…2a6f
4 touches
1 conflict
0x6363986b…fe3a
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
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 0x64800813fa…1bdb9f
Audit this contract →
← previous block·next block →recent activity