← previous blocknext block →recent activity
Analyzing
Block #87,715,485
35 transactions · 34 stateful · 2026-07-14 14:12:48 UTC
Parallelism
48/100
Blocked
59%
Avg conflicts / tx
2.51
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #87,715,485 · 35 txs across 18 waves · depth 18
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
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w25w06w18w29w310w411w512w613w714w819w1220w1326w1429w1532w17
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
20 touches
45 conflicts
0x2385516f…eca5
0x34b655…2a6f
14 touches
21 conflicts
0xbf78ee7f…e7fd
0x34b655…2a6f
12 touches
15 conflicts
0x880fc665…31e3
0x34b655…2a6f
10 touches
10 conflicts
0x0f8965bb…e238
0x34b655…2a6f
10 touches
10 conflicts
0x767799cd…f423
0xc8689a…ee79
10 touches
10 conflicts
0x2c4e81fb…c4c8
0x34b655…2a6f
10 touches
10 conflicts
0x921a58d1…db22
0x34b655…2a6f
10 touches
10 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
45 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity