← previous blocknext block →recent activity
Analyzing
Block #87,351,948
16 transactions · 15 stateful · 2026-07-12 21:40:45 UTC
Parallelism
81/100
Blocked
33%
Avg conflicts / tx
0.56
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,351,948 · 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
3w06w07w18w19w211w012w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x68761f35…6026
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xc36fa358…24cb
0x34b655…2a6f
6 touches
3 conflicts
0xae901867…8085
0x34b655…2a6f
6 touches
3 conflicts
0x471515c5…322b
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x53c9d87e…de85
0x34b655…2a6f
4 touches
1 conflict
0x7da56943…9753
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 0x68761f355d…c46026
Audit this contract →
← previous block·next block →recent activity