← previous blocknext block →recent activity
Analyzing
Block #86,816,510
41 transactions · 36 stateful · 2026-07-10 10:01:00 UTC
Parallelism
61/100
Blocked
75%
Avg conflicts / tx
2.8
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #86,816,510 · 41 txs across 16 waves · depth 16
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w18w19w210w011w112w214w015w116w217w318w419w520w621w722w823w924w1030w131w233w334w435w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
26 touches
78 conflicts
0x7babfe9a…ff96
0x34b655…2a6f
12 touches
15 conflicts
0xb06917e8…6985
0x34b655…2a6f
12 touches
15 conflicts
0x2c8bf7d9…3cc7
0xc8689a…ee79
8 touches
6 conflicts
0x2328941c…84d3
0x34b655…2a6f
8 touches
6 conflicts
0x3a192eef…3c7f
0x34b655…2a6f
8 touches
6 conflicts
0x4f4bdabd…ffba
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
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
78 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity