← previous blocknext block →recent activity
Analyzing
Block #87,587,968
33 transactions · 30 stateful · 2026-07-14 00:00:00 UTC
Parallelism
67/100
Blocked
70%
Avg conflicts / tx
2.45
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #87,587,968 · 33 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w210w211w312w413w514w615w716w818w319w421w523w626w131w932w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0x2e64e234…5cfa
0x34b655…2a6f
14 touches
21 conflicts
0x2f702750…347d
0x34b655…2a6f
14 touches
21 conflicts
0x157dbfb2…4089
0x34b655…2a6f
14 touches
21 conflicts
0x4467ecee…e95b
0x34b655…2a6f
14 touches
21 conflicts
0x4d9858eb…7098
0x34b655…2a6f
14 touches
21 conflicts
0x5170a218…3a84
0xc8689a…ee79
14 touches
21 conflicts
0x63c900f4…2600
0x34b655…2a6f
12 touches
15 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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity