← previous blocknext block →recent activity
Analyzing
Block #86,911,409
17 transactions · 13 stateful · 2026-07-10 20:35:43 UTC
Parallelism
76/100
Blocked
46%
Avg conflicts / tx
0.94
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,911,409 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w37w09w110w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7ee6007b…fd68
0x34b655…2a6f
8 touches
6 conflicts
0x6b2ba712…0214
0x34b655…2a6f
8 touches
6 conflicts
0x5d7f309d…5145
0x34b655…2a6f
8 touches
6 conflicts
0xf324b405…ca30
0x34b655…2a6f
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x922c7ebd…6600
0xc8689a…ee79
8 touches
6 conflicts
0x6e303d0b…01bb
0x34b655…2a6f
6 touches
3 conflicts
0x74888025…a5b8
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x7ee6007b44…92fd68
Audit this contract →
← previous block·next block →recent activity