← previous blocknext block →recent activity
Analyzing
Block #87,714,114
28 transactions · 24 stateful · 2026-07-14 14:03:35 UTC
Parallelism
79/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,714,114 · 28 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
1w03w04w16w07w112w213w314w417w018w119w123w225w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0cf9e21c…9f5a
0x34b655…2a6f
8 touches
6 conflicts
0x94ba9c4a…41d8
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x5bf44783…6166
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x2965e2d6…5800
0x34b655…2a6f
4 touches
1 conflict
0x364289f7…f98a
0x34b655…2a6f
4 touches
1 conflict
0x3c8d99a5…b937
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
6 conflicts on slot 0x0cf9e21c16…439f5a
Audit this contract →
← previous block·next block →recent activity