← previous blocknext block →recent activity
Analyzing
Block #93,683,400
17 transactions · 17 stateful · 2026-08-06 16:39:33 UTC
Parallelism
65/100
Blocked
35%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,683,400 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w110w011w212w313w414w516w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0ae26137…486a
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x1bf8d2af…d140
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x9ba6ae4a…90cb
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
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 0x0ae26137c9…fb486a
Audit this contract →
← previous block·next block →recent activity