← previous blocknext block →recent activity
Analyzing
Block #87,785,868
28 transactions · 26 stateful · 2026-07-14 22:03:44 UTC
Parallelism
43/100
Blocked
69%
Avg conflicts / tx
2.68
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #87,785,868 · 28 txs across 16 waves · depth 16
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w05w16w27w18w29w310w411w512w613w714w816w917w1021w123w1326w1427w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
18 touches
36 conflicts
0x0dd44476…ef40
0x34b655…2a6f
10 touches
10 conflicts
0x4acbdbcf…a8c6
0x34b655…2a6f
10 touches
10 conflicts
0x9001f549…089d
0x34b655…2a6f
8 touches
6 conflicts
0x3fde350e…8d43
0x34b655…2a6f
6 touches
3 conflicts
0x55c2c22c…0474
0x34b655…2a6f
6 touches
3 conflicts
0x5655f5c3…6b75
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4ab
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
36 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity