← previous blocknext block →recent activity
Analyzing
Block #87,716,250
21 transactions · 17 stateful · 2026-07-14 14:17:57 UTC
Parallelism
76/100
Blocked
24%
Avg conflicts / tx
0.33
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,716,250 · 21 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
5w06w111w212w015w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdd36917c…b88b
0x34b655…2a6f
6 touches
3 conflicts
0xc6e33caa…ec53
0x34b655…2a6f
6 touches
3 conflicts
0x8a705be8…7ac4
0xc8689a…ee79
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x085df2c1…305a
0x34b655…2a6f
4 touches
1 conflict
0x1353affc…75e0
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
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 0xdd36917cc2…d4b88b
Audit this contract →
← previous block·next block →recent activity