← previous blocknext block →recent activity
Analyzing
Block #87,667,410
38 transactions · 36 stateful · 2026-07-14 08:51:04 UTC
Parallelism
63/100
Blocked
58%
Avg conflicts / tx
2.03
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #87,667,410 · 38 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w17w012w113w214w315w416w517w618w719w220w823w924w226w1029w330w435w1136w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08330b36…ae29
0x34b655…2a6f
16 touches
28 conflicts
0x4c188934…158e
0x34b655…2a6f
14 touches
21 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0x5b145de0…367c
0xc8689a…ee79
10 touches
10 conflicts
0x21c9fd73…dae4
0x34b655…2a6f
10 touches
10 conflicts
0x3c0c2f32…c3df
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x88cbd993…f3c9
0x34b655…2a6f
10 touches
10 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
28 conflicts on slot 0x08330b3687…a7ae29
Audit this contract →
← previous block·next block →recent activity