← previous blocknext block →recent activity
Analyzing
Block #87,670,309
24 transactions · 23 stateful · 2026-07-14 09:10:26 UTC
Parallelism
79/100
Blocked
35%
Avg conflicts / tx
0.75
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,670,309 · 24 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w410w011w012w115w017w118w222w023w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x08330b36…ae29
0x34b655…2a6f
8 touches
6 conflicts
0x9fd37234…2731
0x34b655…2a6f
8 touches
6 conflicts
0x6d42d870…6630
0x34b655…2a6f
8 touches
6 conflicts
0x3c0c2f32…c3df
0x34b655…2a6f
8 touches
6 conflicts
0x5b145de0…367c
0xc8689a…ee79
8 touches
6 conflicts
0x8d4c0bb9…ccd3
0x34b655…2a6f
8 touches
6 conflicts
0x21c9fd73…dae4
0x34b655…2a6f
8 touches
6 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
10 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity