← previous blocknext block →recent activity
Analyzing
Block #87,758,012
23 transactions · 22 stateful · 2026-07-14 18:57:20 UTC
Parallelism
65/100
Blocked
36%
Avg conflicts / tx
1.26
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,758,012 · 23 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w28w311w412w513w616w417w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x79277877…6098
0x34b655…2a6f
14 touches
21 conflicts
0x3f7d8a09…362c
0x34b655…2a6f
12 touches
15 conflicts
0xea02471d…1542
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xf3d10975…0d07
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xc2cb4b4a…b088
0x34b655…2a6f
8 touches
6 conflicts
0xc36fa358…24cb
0x34b655…2a6f
8 touches
6 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
21 conflicts on slot 0x79277877df…396098
Audit this contract →
← previous block·next block →recent activity