← previous blocknext block →recent activity
Analyzing
Block #87,715,067
24 transactions · 19 stateful · 2026-07-14 14:09:58 UTC
Parallelism
83/100
Blocked
37%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,715,067 · 24 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w07w19w010w112w213w315w017w119w220w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe3f2706b…d3ec
0x34b655…2a6f
6 touches
3 conflicts
0x6c0f0c32…94d7
0x34b655…2a6f
6 touches
3 conflicts
0x0a8f8b9c…3046
0x34b655…2a6f
4 touches
1 conflict
0x0d55d89d…a4ec
0x34b655…2a6f
4 touches
1 conflict
0x1bc07c63…d6ad
0x34b655…2a6f
4 touches
1 conflict
0x270fa94a…95a6
0x34b655…2a6f
4 touches
1 conflict
0x28c180e1…f1e2
0x34b655…2a6f
4 touches
1 conflict
0x3674075e…02b7
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot 0xe3f2706bdc…95d3ec
Audit this contract →
← previous block·next block →recent activity