← previous blocknext block →recent activity
Analyzing
Block #93,290,466
33 transactions · 33 stateful · 2026-08-05 07:44:08 UTC
Parallelism
76/100
Blocked
73%
Avg conflicts / tx
1.58
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #93,290,466 · 33 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
1w02w13w24w25w06w07w18w09w110w211w312w413w114w115w216w418w519w220w121w322w223w624w325w328w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa56e54d0…2d39
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0x66ca3751…6105
0x34b655…2a6f
8 touches
6 conflicts
0x38bdc5d3…a632
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x40c49f…2af0
8 touches
6 conflicts
0xd30f9e74…d404
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
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 0xa56e54d018…f82d39
Audit this contract →
← previous block·next block →recent activity