← previous blocknext block →recent activity
Analyzing
Block #87,504,208
41 transactions · 33 stateful · 2026-07-13 14:39:03 UTC
Parallelism
68/100
Blocked
64%
Avg conflicts / tx
1.76
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #87,504,208 · 41 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w27w09w110w211w014w115w318w119w220w321w422w523w624w725w829w532w636w937w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0x734ee320…caae
0x34b655…2a6f
12 touches
15 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0xafb2524a…0ce4
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0004
0x158622…375e
10 touches
10 conflicts
0x1d946063…ba90
0x34b655…2a6f
10 touches
10 conflicts
0x326f2a00…a2a6
0x34b655…2a6f
10 touches
10 conflicts
0x33649c4f…b327
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
28 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity