← previous blocknext block →recent activity
Analyzing
Block #87,330,967
18 transactions · 17 stateful · 2026-07-12 19:20:29 UTC
Parallelism
72/100
Blocked
41%
Avg conflicts / tx
0.72
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,330,967 · 18 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
1w02w15w06w17w29w110w212w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x680ca7d7…2df4
0x34b655…2a6f
8 touches
6 conflicts
0x8eef368f…aa21
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xe5c67ebc…b03a
0x34b655…2a6f
6 touches
3 conflicts
0x67e40f97…21a8
0x34b655…2a6f
4 touches
1 conflict
0x334b15f3…045c
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
6 conflicts on slot 0x680ca7d7a6…292df4
Audit this contract →
← previous block·next block →recent activity