← previous blocknext block →recent activity
Analyzing
Block #87,518,568
13 transactions · 13 stateful · 2026-07-13 16:15:17 UTC
Parallelism
54/100
Blocked
62%
Avg conflicts / tx
1.54
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,518,568 · 13 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w15w26w37w49w411w412w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe3fbd09c…9f30
0x34b655…2a6f
8 touches
6 conflicts
0xc36fa358…24cb
0x34b655…2a6f
8 touches
6 conflicts
0x4cabb80a…46bf
0x34b655…2a6f
8 touches
6 conflicts
0xc335872c…4214
0x34b655…2a6f
8 touches
6 conflicts
0xf69bf8bb…421f
0x34b655…2a6f
6 touches
3 conflicts
0x00842ba8…bdc6
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xa86351b8…2c5a
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0xe3fbd09ca5…239f30
Audit this contract →
← previous block·next block →recent activity