← previous blocknext block →recent activity
Analyzing
Block #87,078,985
18 transactions · 17 stateful · 2026-07-11 15:15:08 UTC
Parallelism
67/100
Blocked
47%
Avg conflicts / tx
0.67
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,078,985 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w27w08w110w111w212w316w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x1f0a6dbc…e5a0
0x34b655…2a6f
6 touches
3 conflicts
0x1f6661b9…2150
0x34b655…2a6f
6 touches
3 conflicts
0x21c62a26…4761
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x44934f0e…b291
0x34b655…2a6f
6 touches
3 conflicts
0x526b2642…298c
0x34b655…2a6f
6 touches
3 conflicts
0x5ac5ed65…5d6f
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity