← previous blocknext block →recent activity
Analyzing
Block #93,663,269
23 transactions · 21 stateful · 2026-08-06 14:58:20 UTC
Parallelism
78/100
Blocked
52%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,663,269 · 23 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w06w17w28w210w011w112w213w315w421w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x84d2bf96…1eea
0x34b655…2a6f
10 touches
10 conflicts
0x152f8e3d…3da0
0x34b655…2a6f
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x1a5d321d…a474
0x34b655…2a6f
6 touches
3 conflicts
0x310afe2c…83e1
0x34b655…2a6f
6 touches
3 conflicts
0x8a57c929…b1d4
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
10 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity