← previous blocknext block →recent activity
Analyzing
Block #93,505,851
24 transactions · 21 stateful · 2026-08-06 01:47:00 UTC
Parallelism
67/100
Blocked
43%
Avg conflicts / tx
1.33
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #93,505,851 · 24 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w27w011w312w413w517w618w120w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0xb67817f3…bd57
0x34b655…2a6f
10 touches
10 conflicts
0x8cd191b6…2397
0x34b655…2a6f
10 touches
10 conflicts
0xc6000ba5…8d65
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x948836ff…59ab
0x34b655…2a6f
6 touches
3 conflicts
0xab088a08…2ef0
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
28 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity