← previous blocknext block →recent activity
Analyzing
Block #86,809,520
24 transactions · 20 stateful · 2026-07-10 09:14:16 UTC
Parallelism
75/100
Blocked
30%
Avg conflicts / tx
0.42
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,809,520 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w07w19w212w116w317w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc40c8e2b…b832
0x34b655…2a6f
6 touches
3 conflicts
0xc6ed530e…fa7d
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x33f912f5…7e21
0x34b655…2a6f
4 touches
1 conflict
0x38befc08…20c8
0x34b655…2a6f
4 touches
1 conflict
0x3e6563f1…1c23
0x34b655…2a6f
4 touches
1 conflict
0x410b84ab…1dbc
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 0xc40c8e2bad…1fb832
Audit this contract →
← previous block·next block →recent activity