← previous blocknext block →recent activity
Analyzing
Block #87,723,272
32 transactions · 25 stateful · 2026-07-14 15:04:58 UTC
Parallelism
66/100
Blocked
60%
Avg conflicts / tx
1.94
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #87,723,272 · 32 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
2w05w06w112w213w314w415w516w617w718w819w922w623w724w826w927w131w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0x0dd44476…ef40
0x34b655…2a6f
12 touches
15 conflicts
0x7525206c…fbd5
0x34b655…2a6f
10 touches
10 conflicts
0x147259c6…1709
0x34b655…2a6f
10 touches
10 conflicts
0x5b145de0…367c
0xc8689a…ee79
8 touches
6 conflicts
0x255ba9f3…396d
0x34b655…2a6f
8 touches
6 conflicts
0x5e4b65e1…ebe1
0x34b655…2a6f
8 touches
6 conflicts
0x64aaadbf…f9f3
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