← previous blocknext block →recent activity
Analyzing
Block #87,580,508
21 transactions · 19 stateful · 2026-07-13 23:10:07 UTC
Parallelism
76/100
Blocked
63%
Avg conflicts / tx
1.19
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,580,508 · 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
1w02w13w04w15w26w39w010w111w212w313w414w418w219w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0xdb7c435f…f490
0x34b655…2a6f
8 touches
6 conflicts
0x42341814…60f1
0x34b655…2a6f
8 touches
6 conflicts
0x8e507257…71c1
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x2447fab0…811d
0x34b655…2a6f
6 touches
3 conflicts
0xcb2f2739…05ec
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
10 conflicts on slot 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity