← previous blocknext block →recent activity
Analyzing
Block #86,984,164
21 transactions · 18 stateful · 2026-07-11 04:41:48 UTC
Parallelism
67/100
Blocked
56%
Avg conflicts / tx
1.24
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,984,164 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w26w37w48w59w611w012w113w617w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
12 touches
15 conflicts
0x922c7ebd…6600
0xc8689a…ee79
12 touches
15 conflicts
0x63c900f4…2600
0x34b655…2a6f
12 touches
15 conflicts
0xbfdd8306…fa07
0x34b655…2a6f
10 touches
10 conflicts
0xe57232b3…0fbf
0x34b655…2a6f
10 touches
10 conflicts
0x72e9453a…a977
0x34b655…2a6f
10 touches
10 conflicts
0xe3ce9025…da31
0x34b655…2a6f
8 touches
7 conflicts
0xb09132ed…c9dd
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