← previous blocknext block →recent activity
Analyzing
Block #87,753,460
14 transactions · 13 stateful · 2026-07-14 18:26:55 UTC
Parallelism
64/100
Blocked
46%
Avg conflicts / tx
0.93
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,753,460 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w29w110w211w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc616f7f…6178
0x34b655…2a6f
10 touches
10 conflicts
0xc36fa358…24cb
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x648bb928…97f2
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x15928faa…657d
0x34b655…2a6f
6 touches
3 conflicts
0x36890fff…f3d1
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
10 conflicts on slot 0xcc616f7f2b…a56178
Audit this contract →
← previous block·next block →recent activity