← previous blocknext block →recent activity
Analyzing
Block #87,134,541
28 transactions · 25 stateful · 2026-07-11 21:26:18 UTC
Parallelism
86/100
Blocked
48%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,134,541 · 28 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w07w18w29w010w114w115w216w317w320w124w327w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x5aed1bd2…7afa
0x34b655…2a6f
6 touches
3 conflicts
0x1eb0fab5…3517
0x34b655…2a6f
4 touches
1 conflict
0x28387633…e029
0x34b655…2a6f
4 touches
1 conflict
0x3c610031…a65e
0x34b655…2a6f
4 touches
1 conflict
0x7b44c37c…6fc8
0x34b655…2a6f
4 touches
1 conflict
0xa92c8763…6d7f
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity