← previous blocknext block →recent activity
Analyzing
Block #93,677,530
38 transactions · 35 stateful · 2026-08-06 16:10:02 UTC
Parallelism
89/100
Blocked
11%
Avg conflicts / tx
0.18
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,677,530 · 38 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
4w07w18w29w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8c43f2ff…e857
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x9ba6ae4a…90cb
0x34b655…2a6f
4 touches
1 conflict
0xc3baa205…f26e
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x1e829244…94f8
0x34b655…2a6f
2 touches
0 conflicts
0x3ab787fc…6a13
0x34b655…2a6f
2 touches
0 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 0x8c43f2ff31…9fe857
Audit this contract →
← previous block·next block →recent activity