← previous blocknext block →recent activity
Analyzing
Block #86,625,499
57 transactions · 46 stateful · 2026-07-09 12:44:01 UTC
Parallelism
70/100
Blocked
76%
Avg conflicts / tx
2.84
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #86,625,499 · 57 txs across 17 waves · depth 17
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w49w510w111w213w314w616w719w839w844w945w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
22 touches
55 conflicts
0xe6805ef8…e22e
0x34b655…2a6f
18 touches
36 conflicts
0x79781837…043b
0xd32edf…ff58
17 touches
36 conflicts
0x7b3da897…b268
0x34b655…2a6f
16 touches
28 conflicts
0x7cb2f3fa…4836
0x34b655…2a6f
16 touches
28 conflicts
0xac808a27…82db
0x34b655…2a6f
16 touches
28 conflicts
0xb43dc900…22f2
0xa6afd3…d132
16 touches
28 conflicts
0x2c8bf7d9…3cc7
0xc8689a…ee79
16 touches
28 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
55 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity