← previous blocknext block →recent activity
Analyzing
Block #87,911,393
21 transactions · 18 stateful · 2026-07-15 12:03:18 UTC
Parallelism
67/100
Blocked
39%
Avg conflicts / tx
1.1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,911,393 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w212w313w414w515w616w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x72880226…1435
0x34b655…2a6f
12 touches
15 conflicts
0xc36fa358…24cb
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4ab
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xf3d10975…0d07
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0x7c6cfc14…9958
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
15 conflicts on slot 0x7288022679…181435
Audit this contract →
← previous block·next block →recent activity