← previous blocknext block →recent activity
Analyzing
Block #86,674,591
19 transactions · 16 stateful · 2026-07-09 18:13:13 UTC
Parallelism
68/100
Blocked
31%
Avg conflicts / tx
0.63
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,674,591 · 19 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
5w06w18w212w316w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x21082490…de66
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x56b5f5c0…a3ad
0x34b655…2a6f
4 touches
1 conflict
0x5e67eb31…015a
0x34b655…2a6f
4 touches
1 conflict
0x5e67eb31…015b
0x34b655…2a6f
4 touches
1 conflict
0x76c4467d…ce28
0x34b655…2a6f
4 touches
1 conflict
0x8eedf936…a0c3
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
6 conflicts on slot 0x2108249028…bfde66
Audit this contract →
← previous block·next block →recent activity