← previous blocknext block →recent activity
Analyzing
Block #87,714,259
16 transactions · 14 stateful · 2026-07-14 14:04:33 UTC
Parallelism
63/100
Blocked
57%
Avg conflicts / tx
0.75
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,714,259 · 16 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
1w03w04w15w16w28w39w411w214w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x93b6fab0…09d6
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x7aad02c6…b979
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x5311f864…0984
0x754704…b603
6 touches
3 conflicts
0x505b37d8…d3fc
0x34b655…2a6f
6 touches
3 conflicts
0xe214f7d0…5600
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 0x93b6fab01a…2d09d6
Audit this contract →
← previous block·next block →recent activity