← previous blocknext block →recent activity
Analyzing
Block #87,750,116
41 transactions · 37 stateful · 2026-07-14 18:04:33 UTC
Parallelism
59/100
Blocked
62%
Avg conflicts / tx
2.98
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #87,750,116 · 41 txs across 17 waves · depth 17
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
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w211w313w514w615w716w817w918w1019w1120w1223w424w1425w1531w1533w1639w16
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
24 touches
66 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
20 touches
45 conflicts
0xd4702f73…926c
0x34b655…2a6f
18 touches
36 conflicts
0x0ba865dd…a249
0x34b655…2a6f
18 touches
36 conflicts
0x74fd0a9b…3aaa
0x34b655…2a6f
18 touches
36 conflicts
0x5b353877…605d
0x34b655…2a6f
18 touches
36 conflicts
0x91173b78…d64d
0x34b655…2a6f
17 touches
36 conflicts
0x5170a218…3a84
0xc8689a…ee79
16 touches
28 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
66 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity