← previous blocknext block →recent activity
Analyzing
Block #86,922,912
30 transactions · 23 stateful · 2026-07-10 21:52:32 UTC
Parallelism
67/100
Blocked
65%
Avg conflicts / tx
1.17
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #86,922,912 · 30 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w06w07w110w111w012w113w214w315w416w520w521w623w124w229w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
12 touches
15 conflicts
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x757b0543…e087
0x34b655…2a6f
10 touches
10 conflicts
0x7babfe9a…ff96
0x34b655…2a6f
10 touches
10 conflicts
0x2c8bf7d9…3cc7
0xc8689a…ee79
8 touches
6 conflicts
0x3a192eef…3c7f
0x34b655…2a6f
8 touches
6 conflicts
0x45597879…8174
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
15 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity