← previous blocknext block →recent activity
Analyzing
Block #86,385,714
54 transactions · 42 stateful · 2026-07-08 10:00:04 UTC
Parallelism
65/100
Blocked
76%
Avg conflicts / tx
2.13
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #86,385,714 · 54 txs across 19 waves · depth 19
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
wave w18
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w16w28w29w318w019w120w421w022w123w224w325w426w533w236w337w439w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0xfaef08b1…0696
0x34b655…2a6f
18 touches
36 conflicts
0xe47bf62e…b815
0xd32edf…ff58
9 touches
10 conflicts
0x23769ebc…c8ed
0x34b655…2a6f
8 touches
6 conflicts
0x080ec687…da80
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0xba1edffb…323e
0x34b655…2a6f
8 touches
6 conflicts
0xcae41eab…6db0
0x34b655…2a6f
8 touches
6 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
36 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity