← previous blocknext block →recent activity
Analyzing
Block #87,519,000
15 transactions · 13 stateful · 2026-07-13 16:18:12 UTC
Parallelism
67/100
Blocked
31%
Avg conflicts / tx
0.33
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,519,000 · 15 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w110w213w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36fa358…24cb
0x34b655…2a6f
6 touches
3 conflicts
0xf29db88e…d471
0x34b655…2a6f
6 touches
3 conflicts
0x42d169ff…2c03
0x34b655…2a6f
6 touches
3 conflicts
0x57c00e90…540d
0x34b655…2a6f
4 touches
1 conflict
0x681635c6…a300
0x34b655…2a6f
4 touches
1 conflict
0x7478bb8d…8fe2
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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 0xc36fa35805…6f24cb
Audit this contract →
← previous block·next block →recent activity