← previous blocknext block →recent activity
Analyzing
Block #87,739,096
30 transactions · 26 stateful · 2026-07-14 16:50:49 UTC
Parallelism
53/100
Blocked
65%
Avg conflicts / tx
2.47
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #87,739,096 · 30 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w18w09w110w211w312w413w514w615w719w820w921w1022w1123w124w225w127w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0x22fc9794…6e93
0x34b655…2a6f
10 touches
10 conflicts
0x8ae6d2fe…66f4
0x34b655…2a6f
10 touches
10 conflicts
0x80fd3987…2314
0x34b655…2a6f
8 touches
6 conflicts
0x122ea818…6d1a
0x34b655…2a6f
8 touches
6 conflicts
0x94ba9c4a…41d8
0x34b655…2a6f
8 touches
6 conflicts
0x64aaadbf…f9f3
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
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