← previous blocknext block →recent activity
Analyzing
Block #87,316,337
19 transactions · 19 stateful · 2026-07-12 17:42:38 UTC
Parallelism
58/100
Blocked
58%
Avg conflicts / tx
1.68
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,316,337 · 19 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w06w17w28w310w211w312w413w514w615w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36fa358…24cb
0x34b655…2a6f
12 touches
15 conflicts
0xa9f59232…f58c
0x34b655…2a6f
12 touches
15 conflicts
0x8a35acfb…d1ac
0xb1dbf0…c0d3
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x8ca13937…b3ce
0x34b655…2a6f
6 touches
3 conflicts
0x53638800…6a36
0xd32edf…ff58
5 touches
3 conflicts
0x2fa02525…98ca
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
15 conflicts on slot 0xc36fa35805…6f24cb
Audit this contract →
← previous block·next block →recent activity