← previous blocknext block →recent activity
Analyzing
Block #87,794,300
27 transactions · 25 stateful · 2026-07-14 23:00:07 UTC
Parallelism
52/100
Blocked
68%
Avg conflicts / tx
3.3
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #87,794,300 · 27 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
6w07w18w29w310w411w512w613w714w815w916w1017w1119w220w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
24 touches
66 conflicts
0x9465204c…bf37
0x34b655…2a6f
20 touches
45 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
18 touches
36 conflicts
0x28c62bca…b746
0x34b655…2a6f
18 touches
36 conflicts
0x9ae859db…2d84
0x34b655…2a6f
18 touches
36 conflicts
0x5eb187dd…b1d6
0x34b655…2a6f
18 touches
36 conflicts
0x5b145de0…367c
0xc8689a…ee79
18 touches
36 conflicts
0xe4711b30…bb25
0x34b655…2a6f
17 touches
36 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