← previous blocknext block →recent activity
Analyzing
Block #86,925,693
19 transactions · 18 stateful · 2026-07-10 22:11:10 UTC
Parallelism
68/100
Blocked
56%
Avg conflicts / tx
1.05
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,925,693 · 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
1w02w13w04w15w26w37w48w413w114w315w518w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe8377f79…5f5e
0x34b655…2a6f
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x3b787279…727f
0x34b655…2a6f
6 touches
3 conflicts
0x676d5418…85ea
0x34b655…2a6f
6 touches
3 conflicts
0x7accd167…4103
0x34b655…2a6f
6 touches
3 conflicts
0x7babfe9a…ff96
0x34b655…2a6f
6 touches
3 conflicts
0xd1ec0dfd…ccc0
0xc8689a…ee79
6 touches
3 conflicts
0x1321736a…43e3
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
6 conflicts on slot 0xe8377f798f…125f5e
Audit this contract →
← previous block·next block →recent activity