← previous blocknext block →recent activity
Analyzing
Block #87,662,159
39 transactions · 28 stateful · 2026-07-14 08:15:58 UTC
Parallelism
72/100
Blocked
68%
Avg conflicts / tx
1.62
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #87,662,159 · 39 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w19w010w118w219w320w421w522w623w724w825w926w1028w329w430w531w532w236w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
18 touches
36 conflicts
0x745952b2…d90c
0x34b655…2a6f
10 touches
10 conflicts
0x5b145de0…367c
0xc8689a…ee79
8 touches
6 conflicts
0x75b43fdd…8dc1
0x34b655…2a6f
8 touches
6 conflicts
0x8d4c0bb9…ccd3
0x34b655…2a6f
8 touches
6 conflicts
0x91320c47…c941
0x34b655…2a6f
8 touches
6 conflicts
0x9fd37234…2731
0x34b655…2a6f
8 touches
6 conflicts
0xd7fd3b1f…f930
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
36 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity