← previous blocknext block →recent activity
Analyzing
Block #86,831,301
18 transactions · 16 stateful · 2026-07-10 11:40:04 UTC
Parallelism
83/100
Blocked
31%
Avg conflicts / tx
0.39
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,831,301 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w07w19w010w013w114w217w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0f21840f…6cde
0x34b655…2a6f
6 touches
3 conflicts
0xc7ac2c0f…f591
0x34b655…2a6f
4 touches
2 conflicts
0x264b7ada…ff46
0x34b655…2a6f
4 touches
1 conflict
0x3483ab79…8ed3
0x34b655…2a6f
4 touches
1 conflict
0x42aad825…b067
0x34b655…2a6f
4 touches
1 conflict
0x51cdd01c…4ab4
0x34b655…2a6f
4 touches
1 conflict
0x63c900f4…2600
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
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 0x0f21840f7c…c86cde
Audit this contract →
← previous block·next block →recent activity