← previous blocknext block →recent activity
Analyzing
Block #94,868,071
21 transactions · 19 stateful · 2026-08-10 20:15:26 UTC
Parallelism
76/100
Blocked
47%
Avg conflicts / tx
0.86
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,868,071 · 21 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
1w02w13w24w15w36w07w18w210w014w315w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd88c44ab…a216
0xd32edf…ff58
7 touches
6 conflicts
0x612a8656…e330
0x34b655…2a6f
6 touches
4 conflicts
0x4e58deff…c5d0
0x34b655…2a6f
6 touches
3 conflicts
0x948836ff…59ab
0x34b655…2a6f
6 touches
3 conflicts
0xcda18b0b…6a4c
0x34b655…2a6f
6 touches
3 conflicts
0x0fa46bf3…aa72
0x34b655…2a6f
5 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 0xd66696e0dc…230842
Audit this contract →
← previous block·next block →recent activity